Skip to main content
User management controls who has access to your Thread organization and what they can do. Thread uses a simple two-role system: Admin and User (member). Navigate to User Management in the sidebar — the page itself is admin-only.

​
What each role sees

The org-admin role gates the authoring surfaces — the places where guides, programs, and automation get built. Members get the full operating surface. The gate is enforced everywhere, not just in the navigation — every page, action, and API behind an admin surface checks the role. Members still work with what admins build: they supervise runs from the Inbox, see accounts and their state, use Studio documents, and send Broadcast messages to their assigned accounts.
The first person who signs up for an organization automatically becomes an admin. Later signups matching your email domain join as members.

​
Adding team members

Two paths, both landing in the same table:
  • Automatic domain join. Anyone who signs up with an email matching your organization’s domain joins automatically as a member. No admin action required.
  • Invitations. Click Invite User, enter their email, and choose the role they’ll receive. Pending invitations show in their own table below the user list, where you can resend or cancel them; invitations expire if unused.

​
The user table

​
Changing roles

1

Find the user

Locate them in the User Management table.
2

Open the actions menu

Click the menu at the end of their row.
3

Change the role

Choose Make Admin to promote, or Remove Admin Role to demote. The change takes effect immediately.
Admins can publish guides that message real customers, edit Motions and Workflows, and change org-wide settings. Grant the role to people who build and configure — ops leads, implementers — not to everyone who works accounts.

​
Best practices

Keep at least two admins

A single admin is a lockout risk if that person leaves or loses access.

Default to member

Members can run the whole daily loop from the Inbox. Reserve admin for authoring and configuration.

​
Troubleshooting

They have the member role. Those are admin-only authoring surfaces — promote them if they should be building, or leave them as a member if they only need to operate from the Inbox and Accounts.
Their email domain doesn’t match your organization’s domain. Have them sign up with their work email, or send them an invitation from this page.
Find it under Pending Invitations and click resend — a fresh invitation goes out to the same address.
Removing admin access is immediate via Remove Admin Role. For full removal from the organization, contact team@thread.app.

​
What’s next?

Organization settings

Branding, domains, and org-wide configuration.

How Thread works

What admins build and members operate.