Review activity history¶
Use Activity to find recorded actions for yourself, a colleague or your organization. It is a review tool: searching, filtering and changing pages do not repeat the action described in a row.
Availability: these instructions follow the intended Final Screens journey. The inspected frontend currently shows sample records; its live data, filters, paging and access behavior are not yet verified. Do not treat preview counts or names as your organization's history.
Before you start¶
Sign in to the correct workspace and decide what you need to investigate. If you need another person's activity or an organization-wide view, your account must have organization-history access. Personal history is always bound to the account you are using; entering another person's name does not turn it into their history.
Have an approximate date, action or work reference ready. If your question is about a request's current approval, a case's next step or a document's present access, start with that item's own guide. Historical evidence and current work state can differ.
Open and choose a view¶
- In WorkOS, open Operations, then Activity.
- Choose My activity to review actions recorded for your signed-in account.
- Choose Organization when your access permits a broader review.
- Choose Staff member to focus organization history on one person. Select the intended person and check that the person shown and the applied filter agree before interpreting the rows.
The support panel also offers shortcuts such as Review my activity, Review a staff member and Review organization activity. Available destinations still depend on your access. If organization history is restricted, use Review my activity or ask an administrator to assess the access you need.
Staff history means actions started by that person. It does not mean all actions in which they were mentioned, affected, assigned or a recipient. The displayed name and email are historical information, not a current role or employment check.
Narrow the list¶
Use the search field for a useful part of a person's recorded name, action, category or related work reference. The intended organization view labels it Search by person, action, or reference. Personal search stays within your own actions.
Select the filters that matter to your question:
| Filter | How to use it |
|---|---|
| Person | Available for organization/staff review. Select the person who started the action. |
| Category | Narrow to the kind of work involved. |
| Action | Narrow to a recorded action within the chosen category. Change an incompatible action when you change category. |
| Outcome | Distinguish Completed from Access denied. Neither choice is a pending-work queue. |
| Resource | Narrow by the kind of related work, when applicable. |
| Date | Choose the relevant period. The designed default says Last 30 days; it is a screen choice, not a promise that older history never exists. |
Choose Apply filters. Read the selected filters together with the results, and restart your review from the first page after changing them. Category and action choices describe supported kinds of activity; a choice can exist even when there are no matching entries in your period.
If you see No matching activity, widen the date range, correct the person or change a filter. Use Clear filters to remove the narrowing choices. An empty page under a date or person filter does not establish that the workspace has never recorded activity.
Read a row and move through results¶
Read the main action description first, then the category/action context, When, Outcome, and any Resource context. Use the recorded reference to identify the relevant work when one is present. There is no verified activity-history detail or edit action in this read journey; do not expect every row to open a separate drawer or permit a correction.
Results are ordered newest first. The time is when the action was recorded as occurring, not a live indicator that its related work is still in that state. Treat the list as history: it is not a presence, progress or completion dashboard.
Use the previous and next page controls to review more matching entries. The displayed range covers the current page; the total covers the matching result. New records can arrive between reads, so successive pages are not a frozen export. If the order or totals seem inconsistent, refresh the view and repeat the same filters before drawing a conclusion.
Network and device details are conditional. You can see your own recorded sensitive context; another person's context requires additional access. A blank field may mean there is no value or it is withheld. Do not infer a device, location, identity change or deletion from an empty field.
Recover when the result is unavailable¶
| What you see | What to do |
|---|---|
| Loading | Wait for the read to finish. A loading placeholder is not an empty history. |
| No matching activity | Check the workspace, person, period and filters; change or clear them. |
| No recorded activity | Confirm the selected period and scope before concluding there are no relevant entries. Contact support if a known recorded action remains missing. |
| Activity could not be loaded | Use Try again with the same review context. A failed read does not undo the underlying action. |
| Organization activity is unavailable | Use Review my activity if available. Ask an administrator about organization-history access; retries do not grant it. |
| Some context is unavailable | Use the action and time that remain visible. Ask an authorized reviewer if additional context is necessary; do not fill gaps with assumptions. |
The system can withhold an organization read when its required logging step fails. This may look like a temporary failure even when records exist. Do not repeat an approval, send, dispatch or other business action merely to make history appear. Verify the outcome in the originating feature and give support enough context to investigate the missing or delayed history.
If a known action is absent, record the approximate time, chosen view, filters and relevant work reference. Keep the distinction between not visible here, read failed, and action did not happen. Support and administrators need that distinction to investigate accurately.
Review decisions in the right place¶
Saved approval decisions can appear in the same history under their relevant work category. Pending approvals remain in the appropriate work destination, such as Requests. A historical Completed entry may describe recording a decision or queuing a delivery; consult the underlying work to determine what remains to be done.
Return to the overview for the differences between activity history, work-item timelines and business reporting.