How Enterprise works
Know the parts of an organization, what admins see, and how the console and the app split the work.
Feature Updated 19 Nov 2026What Enterprise is
PandaOS Enterprise lets a company run PandaOS for its people from one place. Owners and admins set up the organization in the Enterprise Console. Members keep using the PandaOS app, with the organization's AI, rules and shared content already in place.
The building blocks
| Term | What it is |
|---|---|
| Organization | Your company in PandaOS. An account belongs to one organization only. |
| Team | A group of members. A member belongs to exactly one team. The team decides which models its members can use, the monthly allowance each member gets, and any policy settings that differ from the organization's. Every organization has a default team. |
| Seat | What lets a member use PandaOS. PandaOS grants your organization seats per plan, and you assign them to members. A member without a seat can sign in but cannot use PandaOS. |
| Policy | The rules for what members can use: which AI, which apps and MCP servers, what the agent may do without asking, and what members may share. There is one policy for the organization, and each team can override parts of it. |
| Library | The skills, agents, starters, rules, design systems, apps, MCP servers and plugins your organization shares with members. |
| Role | Owner, Admin or Member. Owners and admins run the organization in the console. Members use PandaOS. |
The console and the app
Owners and admins run the organization in the Enterprise Console at console.pandaos.ai. Members cannot open the console.
Members work in the PandaOS app on their computer. They sign in with the email they were invited with, and the app applies your organization's policy, models and Library for them.
The console sidebar starts with First Steps while setup is open, then Members, Teams, Review queue and Usage. After them come the AI group (Enterprise Cloud only) and the Policies group, then Library and Settings. Some entries hold tabs. Limits has Team defaults, Members and Service accounts, and Apps and MCP has Connected apps and MCP servers. Library has one tab for each kind of item. Each console page has a Learn more link to its page in these docs, and Help at the bottom of the sidebar opens this overview.
Two kinds of organization
| With Enterprise Cloud | Policy only | |
|---|---|---|
| Who runs the AI | PandaOS runs the AI for your organization, on provider keys and models you add | Members use their own AI accounts, as far as your policy allows them |
| Members, teams, invitations, seats | Yes | Yes |
| Policies, Usage, Library | Yes | Yes |
| Models, Provider keys, Service accounts, Limits | Yes, in the AI group | Not shown |
PandaOS sets which kind your organization is. You cannot change it in the console.
What admins can and cannot see
Admins see recorded spend, requests and input and output tokens per member, team, model and day, on Usage. They also see the full content of anything a member submits to the Library for review.
Admins never see members' prompts, chats, files or project content. Those stay on the member's computer.
Examples on these pages
The pages use an example organization called Acme, with a team called Sales. Your console and app show your own names.