The roles
Owner
Owner
Full control of the organization: managing members and roles, billing, and the organization itself. There is a single owner, and ownership can be transferred to another member.
Billing admin
Billing admin
An administrative role just below owner. Manages billing and can create, update, and delete day-to-day resources such as tenants, knowledge bases, documents, agents, and chats.
Developer
Developer
Works with documents and chats without organization-level administration. Developers can inspect knowledge bases and agents, but cannot configure either resource.
Viewer
Viewer
Read-only access across the organization.
What each role can do
Read (R), write/create (W), and delete (D) by resource:| Resource | Owner | Billing admin | Developer | Viewer |
|---|---|---|---|---|
| Organization | R W D | R | R | R |
| Members & roles | R W D | R | R | R |
| Billing | R W | R W | R | R |
| Environments | R W D | R W | R | R |
| Tenants | R W D | R W D | R | R |
| Knowledge bases | R W D | R W D | R | R |
| Documents | R W D | R W D | R W | R |
| Agents | R W D | R W D | R | R |
| Chats | R W D | R W D | R W | R |
The Owner always has full access to everything in the organization. Only the Owner can invite or remove members, assign roles, and revoke invitations.
Ownership and membership
One owner per organization
Each organization has exactly one owner. To hand over control, transfer ownership to another member from the members screen.
The last owner stays
You can’t remove the last owner. Transfer ownership first, and the previous owner can then be reassigned or removed.
Next steps
Invite your team
Add people by email and assign their role.
Teams overview
How organizations, environments, and tenants fit together.
Core concepts
How knowledge bases, agents, chat, and memory relate.
Tenancy for developers
The API-level view of environments and tenants.