Set up
Members and roles
A member is a person with an account in a workspace; their role, owner, admin or member, decides what they can change. Everyone uses agents; owners and admins also run the workspace.
Web chats are private whatever the role: a chat belongs to the person who started it, and admins and owners can't read it. An automation's runs are the exception, visible to anyone who can view that automation. See Security and privacy.
Roles
- Owner: created the workspace. Always has full access. There is one owner, and the role can't be changed, removed or left.
- Admin: manages settings, people and every agent.
- Member: uses agents, and creates and manages their own. Invitations make members unless you choose otherwise.
Settings → Permissions shows the same table as below, read from the code that enforces it.
What each role can do
| Area | Owner | Admin | Member |
|---|---|---|---|
| View settings | Yes | Yes | Yes |
| Workspace name and picture | Edit | Edit | View |
| Agent defaults and company instructions | Edit | Edit | View |
| Workspace connections: models, sandboxes, knowledge, integrations, secrets | Add, edit, delete | Add, edit, delete | View |
| Personal integrations | Their own | Their own | Their own |
| Surfaces (Slack, GitHub and others) | Manage | Manage | View |
| Create agents | Yes | Yes | Yes |
| Edit agents | Any | Any | Their own |
| Open conversations | Their own | Their own | Their own |
| Rename or delete surface threads | Any | Any | Their own |
| Automations: create, edit, run, delete | Their own | Their own | Their own |
| Automations: view | Any | Any | Their own, and those on agents they own |
| Knowledge documents and skills | Add, edit, delete | Add, edit, delete | View |
| Invite people | Yes | Yes | No |
| Make a member an admin | Yes | Yes | No |
| Demote an admin | Yes | Only themselves | No |
| Remove people | Admins and members | Members | No |
| Leave the workspace | No | Yes | Yes |
| Usage | Whole workspace | Whole workspace | Their own |
| Activity log | Yes | Yes | No |
| Sign-in settings | First workspace only | First workspace only | No |
A few rows need more detail:
- Connections. Enabled workspace connections are shared: members choose from them for agents they own. Members can't add, change or remove them, but can add personal integrations that agents use only on their runs. See Integrations.
- Surface threads. A thread from Slack, GitHub, email or texts is open, read-only, to any member who can view its agent.
- Automations. Only an automation's owner edits, runs or deletes it, whatever their role.
- Sign-in settings cover the whole installation, so only owners and admins of the first workspace created on it can change them.
Adapt checks membership and role on every request and again before each tool call, so a role change or removal applies to runs already in progress.
Invite people
- Go to Settings → Members and choose Invite.
- Enter the person's email address, choose Member or Admin, and choose Create invitation link.
- Copy the link and send it to them yourself. Adapt doesn't email it.
The person opens the link and creates an account, or signs in, with the invited email address. A link for another address doesn't work.
- Links expire after 48 hours and work once.
- The link is shown only when you create it. To send a new one, invite the same address again; the new link replaces the pending one.
- Pending invitations are listed on Settings → Members, where you can revoke one. A revoked link stops working right away.
- You can't invite someone who's already a member.
When Google sign-in is on and email and password sign-in is off, invitations aren't used: anyone who signs in with Google on the company domain joins the first workspace as a member.
Change a role
On Settings → Members, choose Make admin for a member. Owners and admins can promote members.
Only the owner can demote another admin. An admin can step down to member themselves. No one can change their own role otherwise: an admin can't promote themselves, and the owner's role is fixed.
Remove people and leave
Removing someone is permanent:
- Their account is retired. Their sessions, sign-in accounts, linked identities and OAuth grants are deleted, and their email address is released.
- Their personal integrations are deleted.
- Their automations pass, paused, to the person who removed them.
- Agents, chats, runs and usage they created stay with the workspace, under their name.
If they come back by invitation, or by Google sign-in on the company domain, they start as a new user.
Owners can remove admins and members; admins can remove members. No one can remove themselves.
To leave a workspace yourself, go to Settings → General. Leaving ends your membership and deletes your personal integrations in that workspace. The owner can't leave.