Use team analytics
Read team-level usage signals without exposing member details or treating metrics as private-content inspection.
Outcome
You can use team analytics to spot workflow patterns, adoption gaps, or sharing risk without over-interpreting the numbers.
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
Team analytics storyboard
Synthetic team analytics frame only. It uses fake aggregate metrics and avoids productivity, surveillance, benchmark, or compliance claims.
Synthetic frame
Team analytics
Start with scope and date range.
Use team analytics 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.
Set team and date scope
Choose the team, workspace, or date range that answers the operational question.
Read patterns, not private content
Use counts, trends, and categories to decide where training, settings, or review guidance may help.
Branch questions
Can you see the team analytics 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/team-analytics Selected issue: A team metric does not match visible history. 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
Use team analytics
Read team-level usage signals without exposing member details or treating metrics as private-content inspection.
Use this guide when the team analytics 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 use team analytics to spot workflow patterns, adoption gaps, or sharing risk without over-interpreting the numbers.
Before You Start
- Use an account with team analytics permission.
- Know the date range and team scope.
- Check whether exports include member names or session titles.
1. Set team and date scope
Choose the team, workspace, or date range that answers the operational question.
Check before you continue: The dashboard scope matches the question.
2. Read patterns, not private content
Use counts, trends, and categories to decide where training, settings, or review guidance may help.
Check before you continue: The next action is about workflow support, not inspecting private documents.
3. Share analytics carefully
Before sharing a screenshot or export, mask member names, session names, and any team-specific notes that are not needed.
Check before you continue: Shared analytics contain only the intended operational context.
Completion Check
- Team/date scope was checked.
- Metrics were interpreted as workflow signals.
- Exports or screenshots were masked before sharing.
Safe Examples
- A synthetic team trend with member names removed.
- A masked usage chart showing only categories.
If You Need Support
Contact support when:
- A team metric does not match visible history.
- A team analytics export contains unexpected private labels.
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: team-analytics Route: /knowledge-base/team-analytics Selected issue: A team metric does not match visible history. 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