Team management: invite teammates and set roles with permissions
Get your team on board fast, then control who can see, edit, and delete what without slowing anyone down.TL;DR
- Invite teammates. Settings → Team Management → Invite Teammate.
- Accept invite. Teammate creates an account with the same email from the invite.
- Access. Use Roles (Admin/Manager/Operator/Custom) + feature permissions.
- Permission levels. Owner (view/edit/delete), Editor (view/edit), Viewer (view), No Access (blocked).
- Deleting messages from a thread. Only users with Owner permission on a phone number’s Inbox Access can delete messages. By default, only Admins have Owner access to every phone line.

How to invite and manage teammates
Invite teammates
- Go to Settings, then click your profile image (top right).
- Open Team Management under Workspace Settings.
Don’t see Team Management? Ask your workspace admin. Your role may not include access.
- Click Invite Teammate, enter one or more email addresses, select a Role, then click Send.

Accept an invitation
- The invite email links to
inbox.messagedesk.com/#/create-account. - The teammate must sign up with the same email that received the invite.
- After signup, they’re automatically added to your workspace and any assigned inboxes.
Update a user’s role or details
- Team Management, then select the user.
- Click Edit Details or Change User Role.
- Choose a new Role from the dropdown.
- Changes save automatically and apply immediately (a refresh may be required).
Remove a user from your workspace
- Team Management, then select the user.
- Click Remove Member, then Confirm.
- Access is revoked immediately.
Manage invitations
After sending invites, you’ll see each user’s status:- ❌ Pending: User hasn’t created an account yet.
- ✅ Joined: User created an account and joined your workspace.
User roles and permissions
Roles are a collection of Permissions (access levels for features/settings).
Default user roles (×3)
1) Admin: full access- All features and resources (including account/billing): Owner
- Can’t be removed by Managers/Operators
- Not editable or deletable (copy to customize)
- Most features: Editor.
- Billing, Workspace Profile, Workspace Settings: Viewer.
- Team Management, Phone Numbers: Editor.
- Relay Management, Developer: No Access.
- Contacts, Contact Properties, Custom Fields, Labels, Message Templates: Editor (Custom Fields: Viewer).
- Relay Management, Developer: No Access.
- Everything else: Viewer.
Default roles and permissions assignments
Default role/permission feature assignment/access
What each permission level grants access to
Permissions let a user create, read, update, and delete information in MessageDesk. MessageDesk offers four permission levels: Owner, Editor, Viewer, and No Access.Custom roles and permissions
Create custom roles for users in your workspace.Create a custom role
- Account → Settings → Team Management.
- Click Create new role, name it. (Optional.)
- Set per-feature access (Owner / Editor / Viewer / No Access).
- Adjust feature access for specific Phone Lines, Labels, Teammate Inboxes, and other Workspace Settings.
- Save changes and apply your new role to teammates.

Edit, delete, or rename a custom role
- Account → Settings → Team Management.
- Click Edit on the custom role you want to edit.
- Click Delete on the custom role you want to delete.
- Update the role name or adjust permissions as needed.
- Save changes to update and apply immediately (users may need to refresh).

Reassign users associated with a custom role before you can fully delete the role.

Custom role templates (examples you can copy)
Support Agent (Frontline)- Features: Contacts/Labels/Templates = Editor. Broadcasts = Viewer. Billing/Settings = Viewer.
- Resource-level: Editor on Support line(s) and Support labels only.
- Features: Contacts/Labels/Templates = Editor. Phone Numbers = Viewer. Relays = Viewer.
- Resource-level: Editor on Dispatch line, Region labels (West/East).
- Features: Broadcasts = Editor. Contacts/Labels/Templates = Editor. Billing/Phone Numbers = Viewer.
- Resource-level: Editor on HR labels (Benefits, New Hire), Viewer elsewhere.
- Features: Everything = Viewer.
- Resource-level: Viewer on All. No Access to Billing if needed.
FAQ
I invited the wrong email. What now?Remove the pending invite from Team Management and send a new invite to the correct email. Unlimited teammates and roles?
Yes. You can invite unlimited teammates and create unlimited custom roles. Each teammate counts as a seat. Role vs. Permission?
A Role is a collection of Permissions. A Permission is the access level for a specific feature or resource. Can I delete a custom role?
Yes. Go to Settings → Team Management, click Edit on the custom role, and select Delete. Reassign any teammates currently using the role before it can be fully deleted. Can Managers delete things?
No. Editors can’t delete. Only the Owner can delete. Who can delete messages from a conversation thread?
Only users with Owner permission on a phone number’s Inbox Access can delete individual messages from a conversation thread. By default, only Admin users have Owner access to all phone lines. To prevent a user from deleting messages, make sure their role does not have Owner permission on that phone line. Use Editor, Viewer, or No Access on Phone number inboxes instead. What happens when a message is deleted?
When an Owner deletes a message, it’s a soft delete. The message is removed from the front end, but MessageDesk retains the message history on the back end. This data is exportable for compliance and record-keeping purposes. Limit someone to one phone line?
Grant Editor on that Phone Number and set others to Viewer/No Access. Can I use phone line extension numbers with MessageDesk?
MessageDesk doesn’t directly integrate with or support texting for phone line extension numbers. You can configure user Roles and Permissions to limit access to certain phone lines. You can also use conversation assignment and Relays to automate who gets assigned to what conversation on any given phone line. See a conversation without line/label access?
Yes. Assignment to the conversation grants Editor on that thread. Restrict to certain labels (e.g., Support: Urgent)?
Grant Editor on that label and set others to Viewer/No Access. Do changes apply immediately?
Yes. Have users refresh to see the updated UI. Who can access Relays by default?
Only Admin users have access to Relays and Zapier by default. Admins can grant Relay Management or Developer permissions to other roles via custom role configuration to unlock those features. Learn more: Relays Overview. Who can build Zapier workflows?
Any user whose role grants Editor or Owner on the Developer feature. Admins have this by default. For other roles, grant Developer access via a custom role. Viewers can’t authenticate Zapier under their own account, so any Zap built or owned by a Viewer will fail to run. See Zapier.
Troubleshooting
Invite not received- Check spam/junk and verify the email address.
- Resend: Team Management → ⋯ → Resend Invitation.
- Still missing? Ask IT to allowlist
messagedesk.comand try again.
- Their role likely has Viewer/No Access for Team Management. An Admin or Manager (Editor) must adjust.
- By default, only Admin users have access to Relays. An Admin must grant Relay Management permissions to the user’s role via custom role configuration.
- The user is likely a Viewer on that feature, or the action requires Owner. Hover for the tooltip, then upgrade access if appropriate.
- Check for assignment (assignment grants Editor).
- Review resource-level permissions (wildcards
*on Labels or Phone Numbers). - Remove any user override that elevates access.
- Ask them to refresh.
- Confirm there isn’t a conflicting override or resource-level restriction.
Team management best practices
- Least privilege first. Start with Operator. Elevate only as needed.
- Prefer roles over overrides. Keep exceptions rare and documented.
- Mirror your routing. If you route by phone line or label, set permissions the same way.
- Quarterly audits. Review who has Owner on Billing, Phone Numbers, and Team Management.
- Onboarding checklist. Invite, assign role, confirm resource-level access, share key labels/lines, verify login.
- Offboarding checklist. Remove member, reassign conversations, review resource permissions, audit roles.

