Roles and permissions
What it is
Section titled “What it is”A role is a set of permissions. Each permission has the form resource:action (for example records:update or dashboards:edit). Everything is denied by default: only what the role grants is allowed.
Base roles:
| Role | What it can do |
|---|---|
| Owner (Dueño) | Everything, including billing and roles. |
| Administrator (Administrador) | Everything except platform billing and exporting the audit log. |
| Editor | Builds collections, flows, scripts, sites, templates and dashboards; does not publish or enable. |
| Member (Miembro) | Runs flows; sees the records of the collections granted to it. |
| Reader (Lector) | Read only. |
How it works
Section titled “How it works”- Go to Settings → Roles (Configuración → Roles) to see the roles or create your own.
- Check the general permissions and, per collection, the actions: read, create, update, delete, export and comment.
- Per collection you can limit the scope to own or assigned records and mark fields as hidden or read-only.
- Assign the role in Settings → Members (Configuración → Miembros).
Rules and limits
Section titled “Rules and limits”- Nobody creates or assigns a role with more permissions than they have.
- The Owner role cannot be edited and the company is never left without an administrator.
- Roles with sensitive permissions require two-step verification.
- API keys, MCP tokens and agents never exceed the permissions of the person or role behind them.
For agents (MCP)
Section titled “For agents (MCP)”list_roles: roles with permissions («resource:action», «#own» when limited to own records) and per-collection access. Their ids are used in transitions, field permissions and recipients.create_role,update_roleandassign_user_roles(scoperoles:write): always ask for confirmation.- Do not retry a permission error through another path: tell the person.