Roles
Your role within the Client decides which sections you see in the sidebar and what you can change. The sidebar hides what doesn't apply to you, and the routes check it: typing the URL of an administrator section when you aren't one sends you back to Agentes de IA (AI Agents).
Below your name, at the bottom of the sidebar, Studio shows your role. It's the fastest way to know which role you're signing in with.
The Client roles
There are four, and Studio writes them in English and lowercase because that's how they come from the identity system.
| Role | Who has it | What they can do |
|---|---|---|
owner | Whoever created the Client. It isn't chosen when inviting. | The same as admin, and is also the only one who can transfer or delete the Client. |
admin | Whoever administers the Client. | Everything in member, plus Infraestructura (Infrastructure), API, and Administración (Administration), depending on what is enabled for the Client. |
member | Anyone who is invited. It's the default value. | Flujos (Workflows), Agentes de IA, and Laboratorio (Lab). |
viewer | Read-only. It doesn't appear in the invitation selector. | View, without creating or modifying. |
When inviting, you can only choose between member and admin; those are the two the selector offers. The other two exist in the model but aren't assigned from this screen.
Super Admin
It's a platform role, not a Client role, and Saptiva staff hold it. It appears as Super Admin at the bottom of the sidebar, in the place where you see your Client role.
It isn't granted from Accesos (Access): don't look for it there. A Client administrator can't make anyone a Super Admin, not even themselves.
A Super Admin works in two modes and switches between them with the Client selector in the top bar:
In Client mode, a Super Admin sees nothing extra: the Plataforma menu disappears, so that inside your Client there are no links that nobody on your team could use. And the ownership rules still apply, so a Super Admin can't open your members' agents or labs either.
The Client selector is the visible sign: a Super Admin always has it; you only see it if you belong to more than one Client.
What each role can do
| Action | member | admin | Super Admin |
|---|---|---|---|
| Create, configure, and test your own agents | Yes | Yes | Yes |
| Share your own agent and revoke access | Yes | Yes | Yes |
| Use agents shared with you | Yes | Yes | Yes |
| Create, edit, and publish workflows | Yes | Yes | Yes |
| View the Client's Todos los flujos (All workflows) | Yes | Yes | Yes |
| Create, share, and delete your own labs | Yes | Yes | Yes |
| Edit a lab shared with you (Editor role) | Yes | Yes | Yes |
| Choose shared credentials in an agent or node | Yes | Yes | Yes |
| Create, edit, share, and delete credentials | Yes | Yes | |
| View the infrastructure Panel (Dashboard) and the Catálogo (Catalog) | Yes | Yes | |
| Invite, change the role of, suspend, and delete members | Yes | Yes | |
| Configure SSO and the Client name | Yes | Yes | |
| Create InferNode API keys (if the section is enabled) | Yes | Yes | |
| Delete another person's agents, workflows, or labs | No | No | No |
| Onboard and manage Clients | No | No | Yes |
owner behaves like admin throughout the table. viewer can view, without any of the creation actions.
Being an administrator doesn't give access to other members' agents or labs: ownership remains personal, and that's why the last row says No in all three columns. An administrator who needs to remove the lab of someone who left the organization does it by suspending the account and asking Saptiva AI for the cleanup, or, before deleting the account, by asking the owner to share the lab.
With SSO
When the Client has SSO, the role can come from the identity provider, but it can only resolve to admin or member. An owner is never downgraded by SSO: if the provider says otherwise, it's ignored, because the Client would be left without anyone able to transfer or delete it. Details in SSO.
The visible sections may vary by Client: Saptiva AI enables menus according to what was contracted. If you don't see a section you expected, ask your administrator before assuming it's an error.
Next step
- Accessing Studio
- Members and roles (for administrators)