Users, roles & teams
ExoHuman separates two independent scopes: the instance role a person has, and the teams they belong to. Joining a team never transfers personal agents, and being an administrator never makes you a member of every team.
Admission
Section titled “Admission”Only people an administrator admits can sign in. In Settings → People and teams → People and invitations, admins:
- add exact email addresses to the email whitelist with a role;
- change roles, suspend and reactivate accounts, and see last activity;
- give a platform account to someone an agent was shared with.
People sign in with a one-time email code or, if configured, through single sign-on. With SCIM directory provisioning, your identity provider creates and suspends accounts automatically.
| Role | Can do |
|---|---|
user | Use agents shared with them in the Workspace: chat, Inbox, rooms, loops, voice, files |
operator | + Dashboard, agent pages and Operations for agents they can access; run tasks and schedules; own MCP/API keys |
creator | + create agents and teams; choose their default runtime; connect a personal GitHub identity |
admin | + manage people, roles, integrations, model providers, policies, modules and appearance; full access to every agent |
Agent quotas
Section titled “Agent quotas”Each role has a default maximum number of agents a person may own: creator 10, operator 3, user 1 (admins are unlimited). Admins change these in Settings → Agents → Quotas and access. Your plan also caps the number of agents on the instance — see Usage limits & budgets.
Creators and admins create teams in Settings → People and teams → My teams. Within a team:
| Team role | Responsibilities |
|---|---|
| Team lead | Renames and deletes the team, manages members, withdraws shared-agent access, sets delegations |
| Member | Uses agents shared into the team and may share their own personal agents into it |
Leads can delegate two responsibilities to members:
- Manage team membership — add or remove ordinary members (not leads);
- Remove shared-agent access — withdraw existing grants (not share someone else’s agent).
The last active lead cannot leave or be demoted. Members are added by existing username; inviting someone new to the instance remains an admin task.
Team model access and budget is configured by an administrator who is a member of the team — see Model gateway & budgets.
Sharing agents
Section titled “Sharing agents”Every agent has exactly one owner. Owners decide who else can use it:
- People — in the agent’s Settings → People, add an email. If the email has an account they get operator-level, interact-only access; if not, they can use the agent from the Workspace with an emailed code.
- Teams — share into a team you belong to; every member can use it.
- External clients — on the Sharing tab, the Restricted ↔ Open access policy decides whether unknown verified people reaching the agent through a public link or channel can chat immediately (Open) or create an access request you approve (Restricted).
| Access | Can |
|---|---|
| Owner | Everything: configure, share, credentials, schedules, delete |
| Shared person or team member | Chat, run tasks, view files (except credential files) and logs |
| Admin | Full access to all agents |
Sharing never exposes the agent’s credentials, but people can use what the agent can do — limit its tools and repository access before sharing it widely.
Removing someone from a team withdraws their team access and the grants they made to it; rejoining does not restore them. Deleting a team never deletes agents.
Public links
Section titled “Public links”Sharing → Distribution → Public links creates chat URLs (https://acme.exohuman.cc/chat/<token>) with an optional name and expiry. Visitors verify their email when the agent requires it; email-verified visitors get per-person memory. Disable or delete a link at any time.
Portal clients
Section titled “Portal clients”The Sharing tab lists the people using the agent through the Workspace. Owners can Log out a person’s sessions; admins can Block someone from the whole platform. Both actions are audited.