Activity history and work-item timelines¶
Activity history helps you answer who performed a recorded action, when it happened and what result was recorded. A work-item timeline helps you follow the events and discussions around a particular request, project, case or record. Use the view that matches your question: these histories have different contents, access rules and ordering.
Draft availability: personal and organization history reads are implemented in the inspected backend. The current frontend uses sample records and local interactions. The guide describes the newer intended Final Screens journey; connected filtering, permissions and deployed availability still need verification. The timeline guide adds shared work-item reading and the intended request journey. Its current public routing and sample frontend limitations are explicit. The history lifecycle guide explains retention, holds, export scope and organization deletion. The assistant guide explains bounded history/feed answers and current access/paging limits. The timeline data and recovery guide explains delayed updates, reconstruction and separate export/deletion scope. Complete publisher coverage and hosted/connected acceptance remain in progress.
The mailbox history explanation distinguishes provider acceptance, Sent-folder verification, missing supporting evidence and recipient delivery. Complete mailbox setup/sending journeys remain a separate unfinished guide.
The messaging history explanation covers conversation, participant and message recording, repeated acknowledgements, affected-person meaning and safe recovery. Complete messaging task journeys remain separately unfinished.
The meeting history explanation distinguishes setup, occurrences, lobby/admission, recording/transcription and prepared file access. These entries are not a complete attendance or file-consumption record; complete meeting journeys remain unfinished.
The document-access history guide explains selected Shared work and correspondence session-creation entries and separate protected-link recording. It covers short-lived links, repeated requests, and why saved history or a view-open metric does not prove file delivery, reading, approval or signing. Full shared document-session journeys remain unfinished.
Choose the right history¶
| Your question | Where to look | What the result means |
|---|---|---|
| What actions were recorded for my account? | Operations → Activity → My activity | Actions started by your signed-in account. It is not every action that affected you. |
| What happened across the organization? | Operations → Activity → Organization, with the required access | Recorded actions across your current organization, narrowed by the selected filters. |
| What actions did one person start? | Staff member activity, with organization-history access | The same organization history filtered to one initiating person. It is not a current staff profile or a record of everything done to that person. |
| What happened to this piece of work? | Its own activity or timeline view | Events associated with that work item. Read the relevant request, project, record or case guidance. |
| What needs my decision now? | The relevant work or approval destination | A historical decision entry is not a pending approval or an instruction to repeat the decision. |
Follow Review activity history for selecting an actor view, or Follow a work-item timeline for events, detail panels and task discussions. Both explain narrowing results and recovering when information is unavailable. How history is recorded explains historical snapshots, rejected records, delivery retries, conditional denied-attempt recording and why organization-history viewing can fail while its access is being recorded.
For task completion, approval decisions, corrections and workflow setup, use Interpret workflow and approval history. It explains why a completed recording is different from a completed request or a passed simulation.
For membership, chairperson and delegation administration, use Interpret approval-body administration history. Its effective dates and affected people have different meanings from the time and person who entered the change.
Understand the entry before drawing a conclusion¶
An entry describes the recorded action and its outcome. Completed means that action completed as recorded; it does not mean the entire request, delivery or project is complete. For example, recording that a dispatch was queued does not prove that its recipient received it. Access denied records a denied attempt; it does not grant access or establish that every other attempt succeeded.
The action description, category and time help establish context. A related item's title or reference may also be available. Missing resource or security details do not erase the action, and they do not prove why that detail is unavailable. Open the underlying work through an authorized journey when you need its current state. Reading history does not grant permission to change the work or inspect its protected contents.
Names and email addresses in history describe the recorded actor. They can differ from today's staff directory. A renamed, transferred or former colleague may still appear in historical choices. The person filter is not a list of everyone currently employed or allowed to use the workspace.
Guidance for managers and executives¶
Use history to investigate a particular sequence or verify that a specific action was recorded. Agree the organization, person, time window and question before interpreting results. Keep those filters with any observation you pass to another authorized reviewer, and distinguish the time of the action from the time you read it.
The displayed total counts matching retained entries. It is not a count of employees, completed cases, successful deliveries, current approvals or hours worked. Repeated legitimate actions can produce separate entries. Different histories can show different totals because they serve different purposes. A page is only part of the result, and new entries can change the list while you review it.
An empty result does not establish that no work occurred. Filters, access, available history and delivery of recorded events can affect what appears. This documentation does not claim complete capture of every platform interaction, permanent retention, a compliance certification, or a productivity measurement from activity counts.
Access, administration and support¶
Personal history is tied to the signed-in account. Organization and staff-member history require additional access. Viewing another person's recorded network or device context requires a separate permission; such context must also exist in the record. A manager's title alone does not establish either permission. Administrators should provide the access required for the review and verify it in the actual workspace.
Support should establish whether the problem is a failed read, a restricted view, no matching entries, or an entry with limited detail. Ask for the view, approximate time, relevant reference and filter choices through the organization's approved support channel. Avoid copying protected descriptions or security details into public channels. The recovery guide explains what readers can check without repeating the underlying business action.
Activity-history viewing has no separately established price or quota in this documentation. Product access, commercial terms and organization policy remain governed by the relevant platform arrangements; a designed screen is not evidence that an environment has enabled it.
Documentation still being completed¶
The history, timeline, recording, lifecycle, assistant and timeline-recovery guides and their internal integration references are source-traced drafts. Shared runtime and lifecycle rules now have a canonical explanation. Complete publisher coverage, hosted projection/lifecycle recovery, retained recovery-data policy, assistant access/paging reconciliation, responsive screen verification and connected reader walkthroughs remain open. The initial reviewer is the platform owner; no audience acceptance or deployment verification has been recorded.