Company
A company is your tenant in Autessa. Everything you create — agents, tools, tables, connectors, apps, keys — lives inside exactly one company, and every request you make executes inside exactly one company. It is the platform's isolation boundary: for people, for resources, for data, and for encryption keys.
The tenant model
When you sign up you get a personal company, and you can create or be invited into others. You always work inside one company at a time — your active scope, switchable from the header — and switching re-scopes the entire builder and all APIs to that company's resources, members, and limits.
Nothing crosses the boundary. A resource in one company cannot see, call, or reference a resource in another; API credentials are minted inside a company and only ever reach that company's resources; and members see only the companies they belong to. When two companies genuinely need to exchange something, that's what the Marketplace is for — an explicit, reviewed packaging step, never ambient access.
Tenant-specific encryption
Your company isn't just logically separated — it's cryptographically separated. Sensitive data is encrypted at rest with AES-256, using encryption keys unique to your tenant: keys are derived per company, so the key material protecting your data is not the key material protecting anyone else's.
Tenant-specific keys protect, among other things:
- Connector credentials — the OAuth tokens and secrets behind every connected account (Gmail, QuickBooks, Notion, and the rest).
- Conversation and execution history — agent and multi-agent conversation logs, copilot sessions, and transaction records.
- Automation payloads — the before/after payloads captured in trigger execution history, webhook execution details, and scheduled-job run history.
- Feature secrets — MCP server credentials, phone configurations, e-signature verification codes, and app authentication material.
All storage is additionally encrypted at rest at the infrastructure level, and every request is company-scoped before it touches any data — the tenant key is the innermost of several layers, not the only one.
Sharing resources inside the tenant
Within the company, every resource answers two independent questions: who can see it (the share level) and what they can do with it (the access level).
Share level — chosen on the resource's Share dialog:
| Share level | Who gets access |
|---|---|
| Private | Only the owner. Every resource starts here. |
| Specific members | Named teammates, each with their own access level. |
| Company-wide | Every member of the company, all at one access level you choose. |
Access level — what a grant allows, in increasing order:
| Level | In general |
|---|---|
| READ | See and use the resource — view an agent and test-run it, read a table's rows, launch an app. |
| WRITE | Change its working state — edit an agent's draft, write a table's rows, edit an app's files. |
| PUBLISH | Ship it — publish and roll back versions. |
| ADMIN | Govern it — share it, delete it, change its structure. |
The owner always holds ADMIN implicitly, and for most resource types only the owner can transfer ownership. The exact meaning of each level varies a little by resource — on a table WRITE means writing rows, on an app READ means launching it — so every resource's guide page carries its own "Sharing and access levels" section; the general model is in Core Concepts.
Roles and access levels compose: a team role decides whether a member can enter an area of the product at all, and access levels decide what they can do with each individual resource inside it.
What lives at the company level
| Concern | Where it's managed |
|---|---|
| Members, roles, and the owner | Team — who's in the tenant and which product areas each person can use |
| Resources and sharing | Every resource is owned by a member and private, shared, or company-wide — see access levels |
| Connected accounts | Connectors belong to the company and power its tools |
| API credentials | API keys, poweruser keys, webhook keys, and OAuth clients are all company-scoped |
| Usage and limits | Metering, budgets, and plan limits are per-company — Usage & Limits |
| Billing | One bill per company — Billing |
Related
- Team — members, roles, and permissions
- Usage & Limits
- Billing
- Core Concepts — scopes, sharing, and access levels
- Authentication — company-scoped credentials