Personal vs Team usage

Every developer should have a Personal workspace. A developer can also belong to one or more company workspaces.

Use the workspace to answer:

• Who paid?
• Who worked?
• Which project?
• Which policy allowed fallback?
• Which audit line should receive the receipt?

Personal work

Use Personal for side projects, experiments, and local use of personal Codex or Claude plans.

Personal behavior:

• personal provider login stays local
• team fallback disabled by default
• OPC or individual plan policy can apply
• company audit logs are not used unless the user explicitly links the repo

Company work

Use a company workspace when the work belongs to a team or customer project.

Company behavior:

• repo should be linked once with qf link
• team wallet, discount, contract, and audit policy apply
• fallback can be allowed by team policy
• usage receipts include workspace/project/seat/device context

Multiple companies

A developer who works for Acme and Beta should use separate bindings:

github.com/acme/backend -> Acme / Backend
github.com/beta/app -> Beta / App
unknown repo -> Personal

Do not use one global key or one global selected workspace to infer payer. The key or relay token must be scoped to the correct workspace/project.

Common commands

qf doctor
qf use personal
qf link --workspace acme --workspace-type company --project backend
qf run -- codex

qf use <company> is only a temporary context hint. It does not authorize team fallback or team billing. Use qf link inside the repository when the work truly belongs to a company workspace.

What if I use a personal Pro/Max plan for company work?

The personal provider session still stays local. Quotaflow records the workspace/project context and can fallback only when team policy allows it. If the company requires centralized billing or audit, link the repository to the company workspace and use team fallback or team-provided credentials.

Do not upload personal Codex/Claude refresh tokens to Quotaflow cloud.

Routing versus usage

Routing pages explain how traffic is selected and when fallback is allowed.

Usage pages explain ownership, payer, project, and audit attribution.

For routing details, see Routing policy. For installation, see Local Connector.