AppsSecurity & Compliance

Security & Compliance · topic

Access control

Roles decide which parts of Autessa a member can use, and every resource starts private, then is shared at Viewer, Editor, Publisher or Admin, with the highest grant winning.

Role-based access control in Autessa: permissions and roles, one Share dialog with four access levels, linked-resource sharing, run identity and partners.

Start free
Share “Vendor payments”AutessaDB tableSample
Add people, teams, roles or everyone at your company
Sam LeepersonOwner ▾
FinanceteamEditor ▾
Developercompany rolePublisher ▾
Alex KimpersonAdmin ▾
General access · Everyone at your companyViewer

Access adds up: each person gets the highest level of any grant.

How it fits together

How does access control work in Autessa?

Access control in Autessa has two layers. Company roles decide which areas of the product a member can use at all; per-resource sharing decides what they can do with each agent, table, app or secret inside those areas. Runs inherit the identity of whoever started them, so automation never widens access.

IN THIS AREA

  • Built-in and custom roles over product permissions
  • Access levels on every resource, highest grant wins
  • Linked resources shared in one reviewed step
  • Runs act as their person, all the way down

In this area

Every access control feature

01Roles 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.→02Sharing and access levelsEvery Autessa resource starts private and is shared from one dialog with people, teams, company roles or everyone, each at its own level, and a person gets the highest level of any grant.→03Sharing what an app usesSharing an app or agent lists every table, tool and agent it uses, gives each only the access it needs (or the same access as the app), never lowers anyone, and saves everything together or nothing.→04Who a run acts asTools, agents, multi-agents and scripts run as the person who started them, into every sub-agent and tool they call, and nothing a run passes along can change who it runs as.→05Partner and consultant accessAn agency or consultant gets only what you switch on, usage, spending or working inside your company as Consultants, and nothing is shared until your company accepts.→

Other areas

The rest of Autessa Security & Compliance

FAQ

Access control: 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 share something with people outside my company?

Not through the Share dialog. Sharing always stays inside your company. To let outside people use an app, choose its hosting mode.

Will sharing an app lower anyone’s access to its tables?

No. Access is only added or raised. Anyone with more access than the app needs keeps it.

Can a tool run with more access than the person using it?

Only a simple data tool that its owner explicitly sets to Run as owner, limited to the one table it is configured for. It turns itself off if anyone else changes it.

Can a partner see my data by default?

No. Only See your usage is selected to start, and nothing is shared until your company accepts. Working inside your company is a separate switch.

Access control, built in

Roles decide which parts of Autessa a member can use, and every resource starts private, then is shared at Viewer, Editor, Publisher or Admin, with the highest grant winning.

Start free

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