Access control
Roles and permissions (RBAC)
Autessa role-based access control (RBAC) groups product permissions, such as Agentic Workflows, AutessaDB, API Keys, Billing and Manage Team Members, into roles. Built-in roles (Admin, Developer, Manager, Accountant and User) cover common jobs, custom roles hold exactly the permissions you choose, and a member with several roles gets all of their permissions.
The problem
What problem does it solve?
An accountant does not need to build agents; a developer does not need the bill. Without roles, everyone sees everything and least privilege is a hope rather than a setting.
How it works
- 1
Invite with roles
Team → Invite Team Member. Enter an email and tick at least one role. Built-in roles are tagged and each shows what it grants.
- 2
Define custom roles
When no built-in role fits, define one with exactly the permissions you want.
- 3
Areas hide without the permission
If a member lacks a permission, its sidebar sections and actions are hidden. App Viewer members see Apps instead of App Builder.
- 4
Remove when they leave
Remove a member from the Team table. It is immediate; the person loses access to the company’s resources.
Every option
Roles and permissions (RBAC): settings and options
| Setting | What it does |
|---|---|
| Agentic Workflows | Tools, Agents and Multi-Agents. |
| AutessaDB | Tables and trigger execution history. |
| Scheduled Jobs, API Keys | Scheduled jobs; API key and webhook-handler management. |
| App Builder / App Viewer | Build apps, or only use published apps. |
| E-Signature, Meeting Recorder, Redact | Everyday collaboration features, in every built-in role. |
| Billing | The company’s billing pages. |
| Manage Team Members | Invite and remove members, assign roles and edit company settings. |
Permissions
Who can do what?
| Who | What they can do |
|---|---|
| Admin | Everything. |
| Developer | Builds across the whole suite; no team or billing. |
| Manager | Runs the team, plus the everyday collaboration features. |
| Accountant | Billing, plus the everyday collaboration features. |
| User | Uses published apps and the everyday collaboration features. |
| Company owner | Sits above roles, always has full access, cannot be removed, and alone can transfer ownership. |
FOR DEVELOPERS
What to know
- An inviter can never grant roles carrying permissions they do not hold, so an invitation never hands out more access than the inviter has.
- Ownership moves only from the owner, only to a member who already holds Manage Team Members and Billing.
Connections
How Roles and permissions (RBAC) connects to the rest of Autessa
Reports, policies and security questionnaires are on the Autessa Trust Center.
FAQ
Roles and permissions (RBAC): questions
What built-in roles does Autessa have?
Admin, Developer, Manager, Accountant and User. Partner teams working inside your company use the built-in Consultant role.
Can I create custom roles?
Yes. Define a custom role with exactly the permissions you want and assign it like any other.
What if someone holds two roles?
They get every permission either role grants. Permissions add up.
Can a manager make someone an admin?
Only if they hold every permission the Admin role carries. You can never grant more than you have.
Get started with Roles and permissions (RBAC)
Autessa includes role-based access control: permissions gate whole areas of the product, built-in roles cover common jobs, and custom roles hold exactly the permissions you choose.
Reports, policies and questionnaires live on the Autessa Trust Center.
100% customizable, code and all
Make Autessa Security & Compliance fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours