What it does
A team is the organisation's, so its work is the organisation's bill. With Company Pays: No Personal Keys or Subscriptions on, every turn in a discussion the team owns (shared with the team, or filed in one of its projects) runs on:
- The team's key for the model's maker, when the team holds one.
- Our Keys, billed to the team's credit.
Never on a member's own API key or Custom endpoint, and never on their own subscription. The owner's own keys are not used either. Guests follow the same order, and so do the side chat, Ask and the warden's checks when they are opened from a team discussion. A cloud run never carries a member's key: its model calls and machine time are billed to the team's credit. All of it counts against the team's credit, each member's budget and the ceiling per discussion.
Seats on a member's own tools
- Your API Key and Custom are held back in the team's discussions, with the reason beside them. A seat set to one keeps its model and runs on the team's key or credit.
- Your CLI (Claude Code, Codex, Gemini CLI) runs only when its own sign-in is an account on the team's verified domain. Otherwise the team covers the seat on the same model and says so, for example: "Your Claude Code is signed in with a personal account; GPUlogy AI covers this seat instead."
- An ACP, A2A or cloud seat of the member's own is covered the same way.
- Free Key still runs: it costs nobody anything. So does Ollama on the member's own computer.
Seats in the team's discussions read Covered by and the team's name on the web, the Mac and the iPhone.
What it leaves alone
A member's own discussions outside the team, auditors (who never run on the team's credit), and a team whose plan has ended (its rules stop applying, this one too).
Where to find it. Governance → Ownership & access. Default: on, for new teams and for teams from before it existed; the owner is told once on the Governance page. Switch it off to let members bring their own keys and subscriptions to team work again; every change is in the audit log.