Member Invitations
What it does: Admins and owners can invite new team members by email. Invitees receive a branded email with a link to join your organization — they sign up (or log in) and are added automatically with the role you chose.
Organization roles
Cumulus uses three org-level roles. Every member of your workspace has exactly one.
| Role | Who has it | What they can do |
|---|---|---|
| OWNER | The workspace creator (one per org) | Full control — billing, org settings, transfers ownership. Cannot be removed by anyone else. |
| ADMIN | Promoted by the owner or another admin | Invite/remove members, change roles, configure org settings, manage integrations and Knowledge Base. Cannot remove the OWNER. |
| MEMBER | Standard team members | Chat, upload personal files, create projects, use connected integrations subject to plan limits. Cannot manage members or org settings. |
There is always exactly one OWNER. Ownership can be transferred, but not shared.
How to invite a member
Only OWNER and ADMIN can invite new members. The Invite Member button is not visible to MEMBERs.
Open the Members page
Go to Settings → Members and click the Invite Member button in the top-right corner.
Enter their email and role
Type the invitee’s email address and choose a role:
| Role | Permissions |
|---|---|
| Member | Can chat with AI, upload files, create projects |
| Admin | Full access including member management and integrations |
Send the invitation
Click Send Invitation. The invitee appears in the members list with a Pending badge.
What the invitee experiences
New users (no existing account)
- They receive an email from Cumulus by Suprvisr AI with a Get Started button
- Clicking the link opens an invitation page showing your organization name and who invited them
- They click Sign up or Log in to Accept
- After creating their account, they’re dropped directly into the 3-step onboarding flow (name, role, features tour) as a member of your organization
Existing users
- They receive the same invitation email
- Clicking the link opens the invitation page
- They click Sign up or Log in to Accept and log in with their existing credentials
- They’re added to your organization immediately and redirected to the app
If an invitee is already logged in when they click the invitation link, acceptance happens automatically — they’re redirected straight to the app without an extra step.
Changing roles
OWNER and ADMIN can change the role of any other member:
- Promote a MEMBER to ADMIN — grants full management permissions immediately
- Demote an ADMIN to MEMBER — removes management permissions immediately
- Transfer ownership — only the OWNER can hand off ownership via Transfer Ownership in Settings. The current owner becomes an ADMIN; the new owner takes the OWNER role.
Last-admin protection: Cumulus will not let you remove or demote the last admin (or the owner) from a workspace. This prevents accidentally locking the organization out of its own settings.
Managing invitations
Pending invitations appear in the members list alongside active members. Admins can:
- Resend an invitation if the link has expired or the invitee didn’t receive it
- Revoke an invitation to cancel it and free up the seat immediately
Use the … menu on any pending invitation row to access these actions.
Invitation links expire after 24 hours. If an invitee clicks an expired link, they’ll see a message asking their admin to resend. Use the Resend action to generate a fresh link.
Pending invitations count toward your seat limit. Each invitation uses one seat from the moment it’s sent. Revoking an invitation frees the seat immediately.
Billing and seats
- Pending invitations are billed from the moment they are sent
- Invitations do not expire automatically — they remain pending (and billable) until the admin revokes them
- The seat counter on the members page shows both active members and pending invitations
- You cannot reduce your seat count below the total of active members plus pending invitations
Project-level editor role
Separately from their org role, each member added to a project (workspace) has an editor flag that controls what they can do within that project:
| Editor flag | What they can do in the project |
|---|---|
| Editor (on) | Edit project sources, update project memory, change project settings |
| Viewer (off) | Read chats and sources; cannot modify project configuration |
This is set per-project when adding a team member to a workspace, and can be changed from the project’s Team tab.
Related
- Workspaces — project-level team and editor settings
- Personalization — individual member preferences
- Admin Setup — full admin configuration guide