Managing Claude Team and ChatGPT Business

ChatGPT Business: roles are not seat types

OpenAI documents Owner, Admin, Analytics Viewer and Member roles, alongside Standard and Premium seat types. Roles govern permissions; seat types govern usage access. A workspace Owner manages paid seat capacity. Removing a person does not reduce billable seats: the Owner also uses Workspace settings, Members, Users, Manage seats; the reduction applies from the next billing cycle. See OpenAI’s current member and seat guide.

Keep an owner responsible for billing and a separate record of who needs administrative access. Before changing a role or a seat, confirm the person’s job and the expected effect, rather than treating “admin” and “premium” as the same thing.

Claude Team: reconcile members and paid seats

Admins and above can export the member list from Organization settings, Members. It includes role and seat type. Removing someone makes their seat available for reassignment but leaves the total seat allocation unchanged. See Claude’s member-management guide.

An Owner or Primary Owner can reduce allocation through Organization and access, Total seats, Manage. Review the effective renewal date and any plan minimum before confirming. Claude’s seat guide explains the current process.

Schedule the right change for the right date

A leaver’s last day, a seat reduction and a subscription renewal can be three different dates. Plan them separately so a billing decision does not leave someone with access longer than intended.

ChatGPT Business. An Owner can arrange a paid-seat reduction in Workspace settings → Members → Users → Manage seats. It takes effect at the next billing cycle, including the next annual cycle for an annual subscription. Removing a member ends their workspace access immediately but leaves the paid seat available. If nobody needs that capacity, arrange the seat reduction separately. See OpenAI’s billing guide.

Claude Team. An Owner or Primary Owner can reduce allocation in Organization settings → Organization and access → Total seats → Manage → Add or change seats. The reduction applies at renewal, including the annual renewal for an annual plan. Removing a member ends their organization access immediately and frees the seat for someone else; it does not reduce the allocation. Claude allows one pending seat change, and another seat change, seat purchase or accepted invitation can replace it. Recheck the pending change after those events. See Claude’s seat guide.

A simple plan you can use without Vaze

1. Record the workspace, owner and decision in your shared working sheet. Keep personal details in controlled company storage.
2. Set an access-change appointment for the person’s agreed leaving time, with a named administrator to carry it out.
3. Set a separate reminder ahead of renewal to reconcile paid capacity and submit any reduction in the provider console.
4. Record the provider’s confirmation and effective date. Check membership after the access change and the invoice after renewal.

Use your existing calendar or task manager for the reminders. Include the workspace and owner, rather than passwords, API keys or sensitive conversations.

Keep the review together in Vaze

Vaze keeps each AI tool’s owner, purpose and next review date in one company register and shows what’s due. Record the decision after a review and set the next date; you can maintain these records without connecting a reporting provider.

In Tools → Your tools, use Edit ownership to set the next review date, then use Review due to find records that need attention.

For supported work in Improve, plan a date and time and download a calendar entry for your team to complete the work.

Use the reports your plan actually provides

Claude Team Owners and Primary Owners can access usage analytics. Claude documents a spend CSV with up to 90 days of history and a daily refresh, with the newest available day being yesterday. Treat that export as a dated source, not a live connection. Its programmatic Analytics API is for Enterprise plans. Check the analytics guide for the report available to your plan.

Keep any member-level export in your company’s controlled storage. Share aggregate findings when that is enough, and keep the period and billing basis with the result. You do not need to upload a raw member or spend CSV to Vaze to keep the review organised.

A short review you can repeat

1. Confirm the owner and plan. Check the correct workspace and who can approve membership and billing changes.
2. Reconcile access. Compare the current members and invitations with joiners, movers and leavers.
3. Check seat decisions. Separate paid capacity, assigned seats and planned changes. Ask the owner before removing access.
4. Review approved uses. Confirm the tasks and data staff may use in the workspace.
5. Close the loop. Record the decision, the next review and when any billing change takes effect.

Fictional example: an eight-person company uses Claude Team. One employee leaves on 16 October and the monthly plan renews on 1 November. Its administrator plans to remove workspace access on the employee’s last day, checks whether a replacement needs the spare seat, and arranges any allocation reduction for renewal. The owner records the review in Vaze and verifies the next invoice. The same routine works with a shared sheet and calendar.

Before choosing capacity for renewal, use the Claude Team and ChatGPT Business seat cost calculator to compare the published seat prices and billing choices.

What to keep in the company register

Record the tool, exact plan, owner, purpose and next review date. In your billing working sheet, keep paid seat count by type, the latest reconciliation date and any scheduled change. Note whether your evidence came from the admin console, an export or a supported reporting connection. Do not store passwords, API keys or staff conversations in the register.

The free inventory CSV gives you a starting record. Our leaver seat guide and small-team routine cover the next steps.

Where Enterprise reporting differs

Vaze offers separate supported connections for eligible ChatGPT and Claude Enterprise workspaces, using authorised workspace administration credentials. Those are not the same as an ordinary developer API key, a vendor CSV export or a Team/Business subscription. See the Enterprise admin reporting guide before arranging a connection.

For Team and Business, keep the tool and its review work in Vaze while using the vendor’s console for administration. Vaze does not automatically synchronise those workspaces’ members, spend or usage, or apply changes to them.

Sources

Membership and seat-scheduling guides checked 9 October 2026; reporting guidance checked 5 October 2026. The linked official OpenAI and Claude guides support the vendor steps above. Admin screens, role availability and billing terms can change; confirm the current provider screen and your contract before making a change.