Documentation · Use
Team and roles
An Operanse account belongs to a person. An organisation holds sites, alerts and billing, and a person can belong to more than one. Invite people from Team in the dashboard; they get an email and join with their own account.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including granting or revoking the owner role and renaming the organisation. |
| Admin | Sites, alerts and the team, but never an owner. |
| Member | Read every site, or only the sites chosen for them; run investigations through an AI assistant; create their own API tokens. |
| Viewer | Read every site, or only the sites chosen for them. |
An organisation always keeps at least one owner. Admins cannot change or remove owners. Making someone an owner gives them every site.
Limiting a person to certain sites
An admin, member or viewer can be limited to a list of sites, now or later. An admin limited this way manages those sites and their alerts, and nothing organisation-wide: not the team, not billing, not the organisation itself. Over MCP, a limited person's assistant sees only those sites.
This is how an agency gives a client access to their own store and nothing else: invite them as a viewer or member limited to that site.
Your account
Account in the dashboard lists your organisations and your active sessions, and is where you close your account. Closing it disconnects the plugin on your sites and removes the data stored for them; if you cannot sign in, email privacy@operanse.com.