Team
The Team page is where you manage who belongs to your company and what they are allowed to do. Invite teammates by email, assign them roles as you invite them, and remove members who should no longer have access.
What it's for
Every Autessa company is a shared workspace. The Team page lists everyone who has accepted an invitation to your company and gives members with the right permission the controls to grow or trim that list. It is also where company-level settings live: renaming the company, choosing how long members stay signed in and, for the owner, transferring ownership to another member.
Navigating here
From the builder sidebar, open the Company section and click Team. The page header shows the current company name along with two buttons:
- Company Settings — rename the company and set how long members stay signed in; the owner also finds the ownership-transfer option here.
- Invite Team Member — visible only if you have the team-management permission.
If a consultant manages your company, a Managed by banner appears at the top of the page; the company owner can revoke the consultant's access from that banner.
Key concepts
- Members — the Team Members table lists each member's name, user ID, and email. Your own row is marked so you cannot remove yourself. The list paginates at 10 members per page.
- Consultants — a consultant is a company-level designation, not a member role. A consultant granted access to your company appears in the Managed-by banner, and the owner can revoke that access at any time.
Roles and permissions
A role is a named bundle of permissions. Autessa ships built-in roles available to every company (tagged Built-in in the invite dialog), and your company can define custom roles of its own. A member can hold more than one role — their permissions are the union of everything those roles grant.
Permissions gate whole areas of the product; if a member lacks one, the corresponding sidebar sections and actions are hidden for them:
| Permission | What it unlocks |
|---|---|
| Agentic Workflows | The Tools, Agents, and Multi-Agents sections |
| AutessaDB | Tables and trigger execution history |
| Scheduled Jobs | Scheduled jobs |
| API Keys | API key and webhook-handler management |
| App Builder | Building apps in the App Builder (implies App Viewer) |
| App Viewer | Using published apps only — the sidebar shows Apps instead of App Builder |
| E-Signature | Document signing |
| Meeting Recorder | The meeting recorder |
| Billing | The company's billing pages |
| Manage Team Members | Inviting and removing members, assigning roles, and editing company settings |
Built-in roles
The five built-in roles map to those permissions like this:
| Permission | Admin | Developer | Manager | Accountant | User |
|---|---|---|---|---|---|
| Agentic Workflows | ✓ | ✓ | |||
| AutessaDB | ✓ | ✓ | |||
| Scheduled Jobs | ✓ | ✓ | |||
| API Keys | ✓ | ✓ | |||
| App Builder | ✓ | ✓ | |||
| App Viewer | ✓ | ✓ | ✓ | ||
| E-Signature | ✓ | ✓ | ✓ | ✓ | ✓ |
| Meeting Recorder | ✓ | ✓ | ✓ | ✓ | ✓ |
| Billing | ✓ | ✓ | |||
| Manage Team Members | ✓ | ✓ |
In practice: Admin holds everything; Developer builds across the whole Autessa suite but doesn't touch the team or the bill; Manager runs the team; Accountant handles billing; User consumes what's been built — launching apps rather than building them. Document signing and the meeting recorder are everyday collaboration features, so every built-in role includes them. When none of these fit, define a custom role with exactly the permissions you want.
Only members with Manage Team Members can invite, remove, or re-role members — and an inviter cannot grant roles carrying permissions they don't hold themselves, so an invitation can never hand out more access than the inviter has.
The company owner sits above roles: the owner always has full access and cannot be removed. Ownership can be transferred only by the owner, and only to a member who already holds Manage Team Members and Billing. On the Companies page, each workspace is badged as Personal, Owner, or Member to show your relationship to it.
Roles decide which parts of the product a member can use at all. Access to individual resources within those areas — a specific agent, table, or app — is governed separately by access levels.
How to invite a teammate
- On the Team page, click Invite Team Member.
- Enter the person's Email Address.
- In the Roles checklist, select at least one role. Built-in roles are tagged, and each role shows a description of what it grants.
- Click Send Invitation. Autessa emails the person a link; once they accept, they appear in the Team Members table.
How to remove a member
- Find the member in the Team Members table. The Actions column is visible only if you have the team-management permission.
- Click Remove on their row.
- Confirm in the Remove Team Member dialog. Removal is immediate and cannot be undone — the person loses access to the company's resources.
How to rename the company or transfer ownership
- Click Company Settings in the page header.
- Edit the Company Name field to rename the workspace.
- If you are the owner, use the Transfer Ownership dropdown to pick another confirmed member — they must already hold the Manage Team Members and Billing permissions. Transferring ownership removes your admin access to the company, so read the warning before you confirm.
- Click Update Company.
How to change how long members stay signed in
Autessa signs a member out after a period without activity. By default that's 1 hour, and any activity in Autessa starts the clock again. The same sign-in covers team-only apps built in the App Builder.
- Click Company Settings in the page header.
- Pick a length in Sign out after inactivity, from 15 minutes to 30 days, or Default.
- Click Update Company.
The setting applies to everyone in the company, including people who are already signed in. A member who belongs to several companies follows the setting of the company they're working in. Longer lengths are convenient on trusted devices but leave an unattended computer signed in for longer. Sign-in is also tied to the network a member signed in from, so switching networks, for example moving from Wi-Fi to a phone connection, still asks them to sign in again.