Team Invites and Roles UX for SaaS
In team products, one user rarely gets full value alone. Inviting colleagues is how an account grows from one seat to many, so the invite flow deserves as much care as signup.
What makes a good team invite flow?
A good invite flow lets users invite several people at once by email, choose a role explained in one plain sentence, see who is pending, and resend or cancel invites. The invitee gets an email that says who invited them and why, and lands in a workspace that already has content. Invites should appear where collaboration starts, not only in settings.
What does a good invite modal look like?
The mock-up shows an invite modal with several emails, a role selector with plain descriptions, and an optional note that makes the invitation feel personal.
Offer invites at natural moments: when a user shares a report, assigns a task, or finishes onboarding. Those prompts get far more use than a ‘Team’ page in settings.
How should roles and permissions be explained?
Start with three or four roles named by what people do, such as Admin, Editor and Viewer, and describe each in one sentence about what they can and can’t do. Show the description where the role is chosen. Add custom roles only when larger customers need them.
| Role | Can | Can’t |
|---|---|---|
| Admin | Manage billing, members and settings | Nothing restricted |
| Editor | Create and edit projects and reports | Change billing or remove members |
| Viewer | View and comment | Edit content |
| Guest | Access only the items shared with them | See the rest of the workspace |
How should pending invites and members be shown?
Show members and pending invites in one list, with status, role and a quick way to resend, change role or remove. Tell admins when an invite has expired.
Seat limits belong here too. Show how many seats are used, and if inviting someone will change the bill, say so before the invite is sent.
Invites are a growth feature.
In team products, the invite flow decides whether one user becomes a customer. Design it like a signup page.
What should the invitee experience be?
The invite email should say who invited them, to what, and why, with one button to join. After joining, the invitee should land on the item they were invited to, not an empty home screen, with a short welcome. Invite emails are covered on transactional emails, the first-run experience on onboarding UX, and billing changes from extra seats on checkout and billing UX.
Frequently asked questions
Where should team invites appear in a SaaS app?
At moments of collaboration, such as sharing or assigning, as well as in team settings.
How many user roles should a SaaS product have?
Three or four at first, such as Admin, Editor, Viewer and Guest.
How should roles be explained?
In one plain sentence about what each role can and can’t do, shown where the role is chosen.
What should an invite email say?
Who invited them, to what, why, and one button to join.
Where should invitees land after joining?
On the item they were invited to, with a short welcome.
Should invites warn about seat charges?
Yes. Tell the admin before sending if an invite will change the bill.