Understand the analytics dashboard
Read analytics as operational signals about Redactorr use, not as proof of private document contents.
Outcome
You can interpret dashboard cards, filters, and trends conservatively and decide what action to take next.
Your progress
Mark each step as you complete it. This is saved only in this browser.
0 / 3 steps complete
Before you start
Visual frame
Review asset
Analytics dashboard interpretation storyboard
Synthetic analytics frame only. It uses fake metrics and avoids productivity, compliance, or customer benchmark claims.
Synthetic frame
Analytics dashboard
Start with scope before reading metrics.
Understand the analytics dashboard workflow frame
Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.
Guided steps
Follow the task, then check the result.
Choose the dashboard scope
Confirm whether the dashboard is showing your work, a team workspace, or an organisation view.
Read trends as signals
Use document counts, review activity, share activity, or pattern usage as prompts for follow-up, not as hidden content evidence.
Review exports before sharing
If you export a dashboard view, check for session names, user names, workspace names, and notes before sending it onward.
Branch questions
Can you see the analytics dashboard surface described in this guide?
Did the result match the completion check?
Completion check
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/analytics-dashboard-explained Selected issue: Dashboard scope appears wrong. 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
Understand the analytics dashboard
Read analytics as operational signals about Redactorr use, not as proof of private document contents.
Use this guide when the analytics dashboard 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 interpret dashboard cards, filters, and trends conservatively and decide what action to take next.
Before You Start
- Use an account with permission to view analytics.
- Know whether you are looking at personal, team, or organisation scope.
- Avoid exporting analytics before checking for private names or session titles.
1. Choose the dashboard scope
Confirm whether the dashboard is showing your work, a team workspace, or an organisation view.
Check before you continue: The scope matches the question you are trying to answer.
2. Read trends as signals
Use document counts, review activity, share activity, or pattern usage as prompts for follow-up, not as hidden content evidence.
Check before you continue: You can name a follow-up action based on the trend.
3. Review exports before sharing
If you export a dashboard view, check for session names, user names, workspace names, and notes before sending it onward.
Check before you continue: Any exported analytics are safe for the intended recipient.
Completion Check
- Dashboard scope was confirmed.
- Trends were interpreted conservatively.
- Exports were reviewed before sharing.
Safe Examples
- A masked dashboard screenshot.
- A synthetic monthly trend with no user names.
If You Need Support
Contact support when:
- Dashboard scope appears wrong.
- A metric conflicts with the visible activity history.
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.
- Article slug
- Selected issue
- Screen name
- Action name
Redactorr support case Source: Article playbook: analytics-dashboard-explained Route: /knowledge-base/analytics-dashboard-explained Selected issue: Dashboard scope appears wrong. 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.
- 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
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions