Skip to main content

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.

Teams are how PANTA OS reflects your organization’s structure. They drive budgets, Library scoping, and analytics. A user can belong to one or many teams.

​
What teams give you

Budget allocation

Token budgets divide cleanly along team lines.

Library scoping

Some assistants visible only to their team; others workspace-wide.

Analytics

Usage and adoption metrics roll up per team.

Champions per team

Each team can name a champion who curates its corner of the Library.

​
Creating a team

Settings → Teams → New

Available to admins.

Name and describe

Use the same name your organization uses internally.

Add members

Pick existing users or invite new ones.

Set the team budget

A slice of the workspace token budget.

Optionally appoint a team admin

Someone empowered to manage the team without full workspace admin rights.

​
How team membership shapes the experience

A user’s team’s assistants surface first in the Library. The rest of the workspace catalog is still searchable.
When a team’s budget is hit, expensive operations are gated for its members.
Admins see per-team adoption, spend, and outcomes.
Users in multiple teams accumulate access. Policies stack permissively unless explicitly restricted.

​
Patterns that work

Mirror the org chart

Map teams to real reporting lines. Avoid invented “AI teams” — they age badly.

Keep teams small

5–25 users per team is the sweet spot for budget alignment and analytics signal.

One champion per team

A named person in each team owns adoption and Library curation.

Review quarterly

Reorganizations happen. Update teams to match.