> For the complete documentation index, see [llms.txt](https://docs.emseapea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emseapea.ai/admin-guide/users-and-roles.md).

# Users and roles

emseapea has three roles per organization:

| Role          | Can                                                                                                                                                            |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Builder**   | Submit app requests, see their own apps, use the MCP tools                                                                                                     |
| **Approver**  | Everything a builder can, plus decide requests and sign off sensitive deploys                                                                                  |
| **Org admin** | Everything an approver can, plus settings, connectors, integrations, decommissioning — and only admins may decide requests that ask for off-allow-list systems |

## Inviting someone

Settings → members (or the API) sends an email invitation carrying an expiring token and the role you chose. The invitee signs up (or in), accepts, and lands with exactly that role. Re-invite and revoke are one click.

## A person in several orgs

An account is global; membership is per-org. Someone who belongs to two organizations sees the org badge become a switcher — switching is a full context switch: different data, different role, different navigation.

Every membership change is an event in the audit log.