PANTA OS uses a clear, role-based model. Every user has a role; every role has clear capabilities. No surprises.Documentation Index
Fetch the complete documentation index at: https://help.pantaos.com/llms.txt
Use this file to discover all available pages before exploring further.
The roles
Member
Use any assistant or workflow visible to them. Post in Community. Manage their own favorites.
Builder
Everything a Member can do, plus: create and edit assistants and workflows, manage knowledge bases, publish to the Library.
Team Admin
Builder rights, plus: manage their team’s users, budgets, and Library curation.
Workspace Admin
Full control — branding, identity, organization-wide budgets, all users, audit access.
What each role can do
| Action | Member | Builder | Team Admin | Workspace Admin |
|---|---|---|---|---|
| Use assistants & workflows | ✓ | ✓ | ✓ | ✓ |
| Post in Community | ✓ | ✓ | ✓ | ✓ |
| Build assistants & workflows | — | ✓ | ✓ | ✓ |
| Upload to knowledge base | — | ✓ | ✓ | ✓ |
| Publish to Library | — | ✓ | ✓ | ✓ |
| Manage team users | — | — | ✓ | ✓ |
| Manage team budget | — | — | ✓ | ✓ |
| Workspace settings | — | — | — | ✓ |
| Identity provider | — | — | — | ✓ |
| Audit logs | — | — | — | ✓ |
Visibility scopes
Roles control what users can do. Visibility controls what users can see.Private
Private
Only the creator (and explicit collaborators) can see and run the item.
Team
Team
Everyone in the creator’s team can see and run.
Workspace
Workspace
Everyone in the workspace can see and run.
Featured
Featured
Workspace-wide, plus promoted on the Library home.
Best practices
Default to Member
Most people don’t need build rights. Promote on demand.
2–3 Workspace Admins
Enough for coverage; small enough to stay aligned.
Team Admin per team
Distributes admin work without giving away full keys.
Quarterly audit
A 15-minute review of role assignments per quarter keeps things tidy.
Role changes are logged. Audit logs show who promoted whom, when, and why — critical for compliance reviews.