Invite teammates and manage roles
Invite teammates and choose roles without exposing document content or giving broader access than intended.
Outcome
You can invite the right person, choose an appropriate role, and check access before sharing team work.
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 invites and roles storyboard
Synthetic team frame only. It uses fake teammate addresses and avoids exposing real team size, people, or permissions.
Synthetic frame
Invite teammate
Confirm the person before assigning access.
Invite teammates and manage roles 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.
Confirm the recipient
Check the email address and organisation context before sending an invite.
Choose the smallest useful role
Pick the least-privileged role that lets the teammate do their job. Avoid admin-level access for routine review work.
Review pending and accepted invites
Check pending invites and remove mistakes before sharing team sessions, patterns, or packages.
Branch questions
Can you see the team management 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-invites-roles Selected issue: An invite does not arrive after checking the address. 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
Invite teammates and manage roles
Invite teammates and choose roles without exposing document content or giving broader access than intended.
Use this guide when the team management 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 invite the right person, choose an appropriate role, and check access before sharing team work.
Before You Start
- Use an account with permission to manage team members.
- Confirm the teammate email before inviting.
- Know what access the person needs before choosing a role.
1. Confirm the recipient
Check the email address and organisation context before sending an invite.
Check before you continue: The invite target is the person you intended to add.
2. Choose the smallest useful role
Pick the least-privileged role that lets the teammate do their job. Avoid admin-level access for routine review work.
Check before you continue: The selected role matches the teammate task.
3. Review pending and accepted invites
Check pending invites and remove mistakes before sharing team sessions, patterns, or packages.
Check before you continue: Only intended teammates have access.
Completion Check
- The invite email is correct.
- The role is intentionally chosen.
- Pending invites and active members were reviewed.
Safe Examples
- [email protected] as a fake invite.
- A role comparison using synthetic names.
If You Need Support
Contact support when:
- An invite does not arrive after checking the address.
- A role change does not apply as expected.
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-invites-roles Route: /knowledge-base/team-invites-roles Selected issue: An invite does not arrive after checking the address. 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