Private Preview
Join Waitlist →

View history and audit trail

Understand activity history as a record of actions taken, not as a substitute for compliance advice.

Updated 31 May 20265 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: May 2026

Outcome

You can find the relevant action record and decide whether it is enough for your internal review process.

Your progress

Mark each step as you complete it. This is saved only in this browser.

0 / 3 steps complete

Before you start

Know the approximate document, session, or action you are looking for.
Use only records you are authorised to view.
Understand that reports support review but do not certify compliance.

Visual frame

Review asset

History and audit trail storyboard

Synthetic history frame only. It presents activity history as workflow evidence, not legal advice or certification.

ScopeSession or date range
RecordAction names only
ExportReview before sharing

Synthetic frame

Activity history

Start with the question you need to answer.

SessionSupplier invoice review
Date rangeThis week
Action typeExport events
History is easier to trust when the scope matches the question.

View history and audit trail workflow frame

Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.

FindChoose the history scope
DecideRead action names carefully
VerifyExport only if appropriate

Guided steps

Follow the task, then check the result.

Choose the history scope

Start with the document, session, date range, or action type that matches your question.

Success check: The history view is filtered to the relevant work.

Read action names carefully

Use action names, timestamps, and route labels to understand what happened. Do not infer more than the record shows.

Success check: You can explain the action without guessing about hidden content.

Export only if appropriate

If export is available, check the file for private names, session titles, and internal notes before sending it onward.

Success check: Any exported history has been reviewed for safe sharing.

Branch questions

Completion check

The history scope matches the question.
The action record is interpreted conservatively.
Any exported record was checked before sharing.

Support boundary

Support can use by default

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Intent ID
  • Article slug
  • App route

Requires your consent

  • User-written description
  • Email address
  • Explicit attachment
  • Redacted sample
  • Support bundle previewed to the user

Not collected by default

  • Raw original document text
  • Full local file paths
  • Pasted private content
  • Unmasked screenshots
  • Replay capture

Safe support summary

Copy a scrubbed handoff.

Redactorr KB support summary

Article: /knowledge-base/history-audit-trail
Selected issue: A known action is missing from the history view.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Intent ID
- Article slug
- App route

Requires explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture

User note:
- Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.

Article details

View history and audit trail

Understand activity history as a record of actions taken, not as a substitute for compliance advice.

Use this guide when the history or audit trail surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.

Outcome

You can find the relevant action record and decide whether it is enough for your internal review process.

Before You Start

  • Know the approximate document, session, or action you are looking for.
  • Use only records you are authorised to view.
  • Understand that reports support review but do not certify compliance.

1. Choose the history scope

Start with the document, session, date range, or action type that matches your question.

Check before you continue: The history view is filtered to the relevant work.

2. Read action names carefully

Use action names, timestamps, and route labels to understand what happened. Do not infer more than the record shows.

Check before you continue: You can explain the action without guessing about hidden content.

3. Export only if appropriate

If export is available, check the file for private names, session titles, and internal notes before sending it onward.

Check before you continue: Any exported history has been reviewed for safe sharing.

Completion Check

  • The history scope matches the question.
  • The action record is interpreted conservatively.
  • Any exported record was checked before sharing.

Safe Examples

  • A fake audit entry with a synthetic session name.
  • An action list where document titles are redacted.

If You Need Support

Contact support when:

  • A known action is missing from the history view.
  • An action name appears to contradict the product state.

Include only support-safe context:

  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.

Still stuck?

Copy a safe article handoff.

Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.

Support can start here
  • Article slug
  • Selected issue
  • Screen name
  • Action name
Redactorr support case

Source: Article playbook: history-audit-trail
Route: /knowledge-base/history-audit-trail
Selected issue: A known action is missing from the history view.

Safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-redacted sample only after review.
- Article slug
- Selected issue
- Screen name or article section
- Action name

Only include with explicit consent:
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user

Do not include by default:
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
- Hidden diagnostic uploads

User note:
- Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.

Support case builder

One case format, wherever you start.

This is the same support case shape used by diagnostics and article handoffs.

Safe to include
  • Article slug and selected workflow step.
  • Screen or action name.
  • Browser, viewport, workspace type, and file type category when relevant.
  • Synthetic sample shape or already-redacted sample only after review.
  • Article slug
  • Selected issue
Consent boundary

Private material belongs behind an explicit consent step, not in the initial case.

6 default exclusions

Before you copy0/4 ready
Open safe support guide