Who this is for: Teams explaining workspace invitations.
What to prepare
- Invitation screens
- Role definitions
- Pending-status evidence
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second illustrative invitation workflow using a dedicated sample workspace. Identify the inviter’s required role before opening the real invitation control. Use the fictional display name “Example teammate” and the reserved sample address teammate@example.com in planning assets; do not send a real invitation. Show the verified role choices and select the intended Contributor role only if that label exists. Explain what the supplied product documentation says that role permits, without broad security claims. Activate the illustrated send action using supplied states and end on the real pending-invitation label. Use “Invitation pending” rather than “Teammate joined.” Add an accepted state only if a separate acceptance flow is supplied and clearly shown. Keep identity and role visible in the result.
Make it your own
- Sample identity
- Use a fictional name and non-live planning address.
- Assigned role
- Use the exact role label and verified capability boundary.
- Final status
- Match pending, accepted or another observed state precisely.
Verify who can invite
Supply the inviter’s actual permission and any workspace prerequisites. A screen captured as an administrator should not be relabeled as an ordinary member. Confirm the role meaning instead of inferring it from its name.
Adapt the handoff
For an inviter tutorial, end at pending and explain the next person must accept. For a full onboarding lesson, add a separate recipient segment with explicit account labels. Do not collapse both people into one continuous cursor action.
Correct status language
Replace “Added to the team” if the product has only queued an invitation. If the role is changed after sending, show the actual update and its confirmation. Keep the sample address out of any live action; this brief describes illustrative assets.
Review checklist
- The inviter’s permission is stated.
- Role selection remains readable.
- Pending is never mislabeled as accepted.
Sources & further reading
- IANA example domains
IANA maintains example.com for illustrative documentation. The sample address is for planning assets, not a real invitation or a claim of mailbox availability.