Set up company AI accounts by choosing a managed business workspace, paying through the business and inviting each person with a named work identity. Assign ownership and recovery responsibilities, move only approved business material, then test access and staff removal before stopping the old personal-account workflow.
A work email address alone does not prove that an AI account belongs to a company workspace. You need to confirm the workspace, member list, billing and administrator access. Likewise, paying an employee's personal subscription does not by itself give the business control of their chats, connected apps or recovery process.
Build an account register before buying another subscription
Ask everyone who uses AI for work to list the tool, sign-in identity, plan, payment method, work performed and any connected business services. Collect the account facts, not their passwords or personal conversations. Explain that the purpose is to keep useful work available and make the approved route easier to use.
Add an owner and a next action to every row. “Used occasionally” is not enough information if that account contains the only version of your customer reply instructions. Separate essential business assets from old experiments so the move does not become a project to preserve every chat ever created.
For each tool, establish whether staff use individual accounts, a shared password or a managed workspace with separate members. A managed workspace is an organisational area where the business administers access and settings. It still needs someone to maintain it; buying the plan does not complete the work.
| Illustrative register entry | Current problem | Agreed action |
|---|---|---|
| Reception assistant: personal paid AI account | Approved reply wording exists only in private chats | Copy approved wording to the company reference folder |
| Owner: work email on an individual plan | Payment exists, but no company member register | Create or join the agreed business workspace |
| Freelancer: own tool and account | No agreed boundary for customer information | Agree permitted material and access before the next task |
| Old shared login | No clear user or recovery owner | Replace with named access and review existing sessions |
If staff have been using unapproved tools, keep this exercise practical. Ask what task they were trying to finish and provide a workable alternative. The tutorial on reducing unapproved AI use covers that conversation. An account migration fails when people keep using personal logins because the new route cannot do their daily work.
Choose the workspace and calculate the seat bill
Use ChatGPT Business if that is the assistant you have chosen for team work; use Claude Team if Claude is the better fit. Do not buy both simply to establish company ownership. If your work already happens in Microsoft 365 or Google Workspace, first assess the AI access available through your existing managed accounts.
At USD list prices, ChatGPT Business Standard costs $25 per user a month on monthly billing or $20 per user a month billed annually. Claude Team Standard has the same seat prices. Both require a minimum of two seats, so a sole trader choosing either business plan must budget for two.
ChatGPT Business and Claude Team do not use business content for model training by default. This is one account-level distinction, not permission to upload every business record. You still need to decide what staff may enter, which third-party connections are allowed and where approved results should be stored.
Write your must-have administration requirements before choosing a plan. Include named members, a recoverable owner account, a manageable bill and a workable departure process. If you need central sign-in, automated member removal, particular audit records or retention controls, verify those exact requirements for the plan. Do not assume an Enterprise feature is included in a small-team subscription.
Two examples show why. ChatGPT Business includes single sign-on, but OpenAI's user lifecycle guidance lists SCIM directory sync (users added and removed automatically from your staff directory) under Enterprise, Edu and Healthcare only. On Business you invite and remove people by hand, which is fine for a team of eight and tedious for a team of 80. Size limits differ as well: ChatGPT Business is capped at 200 paid seats, and Claude Team runs from 2 to 150.
A four-person nail salon moves in two controlled sessions
In this illustrative migration, a nail salon has an owner, a manager and two reception staff. Three people use personal ChatGPT Plus accounts for work, costing $60 a month at the $20 monthly list price. The fourth person borrows the manager's output rather than having an account.
The salon chooses four ChatGPT Business Standard seats on monthly billing, costing $100 a month. The recurring increase is $40 if the three old work-funded subscriptions are stopped. The reason for the move is named company access and a shared operating process; the calculation makes no claim about time savings.
The owner allows 90 minutes for inventory and workspace administration, 20 minutes for each of four people to sign in and practise, and 30 minutes for acceptance checks. That is 200 minutes, or three hours and 20 minutes. At an illustrative internal rate of $30 an hour, the setup represents $100 of staff capacity, separate from subscription costs.
The first session creates the workspace and prepares the approved service menu, cancellation wording and reply examples. The second confirms each person's access using a fictional booking enquiry. Real customer information stays out of the test. The existing reply process remains available until the new one passes.
The manager finds 14 useful reply examples in personal chats. Only nine are still correct. Those nine are reviewed and saved in a company-controlled document; the other five are not imported merely because they exist. The migration therefore improves the reference material rather than carrying stale wording into a new account.
Create company ownership before sending invitations
- Confirm the business identity. Use a named work account whose email and recovery arrangements the business can support. Check that the business controls the work email service. Avoid making an outside contractor the only route back into the workspace.
- Create the intended business workspace. Follow the current sign-up flow for the business plan, give the workspace a recognisable company name and confirm the chosen seat type and billing term before paying.
- Record billing responsibility. Use the approved business payment method. Record who checks invoices, approves additional seats and handles renewals. Keep this information in the business's account register.
- Assign an accountable owner and a backup. Give ordinary users ordinary access. Arrange a second authorised person who can perform the necessary recovery or administration tasks, using the roles actually available on your plan.
- Secure sign-in before adding business context. Set up the available additional authentication protection and a business-approved recovery process. Test that the right people can use it without sharing credentials.
In ChatGPT, a seat and an administrative role are different things: the seat governs product access, while the role governs administrative authority. A staff member who needs drafting access does not automatically need authority to change company settings. Use that distinction when allocating access instead of making everyone an administrator to avoid support questions.
For example, an illustrative wedding planner signs up using a work email and assumes the job is finished. The account register still has no workspace owner, member list or shared billing decision. The correction is to inspect the actual workspace and invite the intended people, not merely reimburse that person's subscription.
Keep recovery instructions outside the AI account they recover. A note stored only in the owner's private chat is useless during a lockout. The practical guide to additional sign-in protection helps with this part of setup. Never put recovery codes into a prompt or a team message.
Invite named staff and verify the workspace they enter
For ChatGPT Business, use workspace member administration to send individual invitations to the intended work identities. Have each person accept their invitation and confirm that they have entered the intended business workspace. Check the member list afterwards; an invitation sent is not the same thing as a person successfully joining.
OpenAI's user lifecycle guidance distinguishes workspace access from sign-in and from access to connected services. Apply that distinction to your checklist. A successful login does not establish that the person has the correct seat, the right role or access to the files needed for their task.
Use a short acceptance task: open the approved instructions, answer a fictional enquiry, save the reviewed result in the shared business folder and sign out. Ask the person to identify the workspace before they start. If they cannot tell whether they are in a personal or business context, fix that confusion before introducing customer data.
An illustrative barber shop previously used one paid login for three people on reception. A new member system costs more than that single subscription, but keeping the shared login defeats the purpose of the move. Give each authorised user named access and remove the old shared route after checking what business material needs to be preserved.
A personal trainer has a different problem: the browser opens the personal account by habit even after the company invitation is accepted. Use a clearly named work browser profile or another approved separation method, and make the workspace check part of starting a task. Do not assume that accepting one invitation changes every existing browser session.
Move useful work without importing private history
Start with a short asset list: approved prompts, current service facts, style instructions, reusable examples and final business documents. Recreate these in the company workspace from authorised source files. Keep the business's original reference folder as the main record, so the AI tool does not become the only place that knowledge exists.
Do not ask staff to hand over entire personal chat histories. They may contain unrelated private material or information from other work. If the product offers a merge or migration option, read its current explanation of ownership, reversibility, export and access after departure before choosing it. Do not assume that a migration is simply a reversible copy.
For the salon example, the team creates a shared reference document with nine approved replies and a clear version date. Each reply states its intended situation. “Late arrival” and “missed appointment” stay separate, because they have different approved responses. A neat account structure cannot compensate for muddled policy wording.
An illustrative tattoo studio brings in a freelance designer for one project. The designer needs the approved brief and reference images, not the whole client archive. Give access only to the agreed material, record an end date and check the finished files are stored where the studio can retrieve them. A paid seat is not a reason to share every project.
Before ending any old work-funded subscription, confirm which business assets have been preserved and whether another workflow depends on it. Do not promise that cancellation, workspace removal and deletion are the same event. Record each action separately and check the vendor's current handling where retained content matters.
Approve connected apps as a separate access decision
Connecting a file store or inbox introduces another access boundary. Write down the app, the account used to connect it, the business purpose, the permitted material and who will remove the connection later. Begin with the smallest approved scope that makes the task useful.
ChatGPT calls its connected integrations apps. Their administration and available controls depend on the workspace. Check what a connection can read or change before allowing it. The fact that business content is not used for model training by default does not tell you which external app has access or what that app's terms allow.
For example, an illustrative wedding planning assistant proposes connecting the owner's entire drive to find standard proposal wording. The actual need is one approved reference folder. Ask whether the connection can be limited appropriately, or supply only the approved documents. If the available control does not meet the requirement, leave the broader connection off.
Use the tutorial on checking apps with business-account access for the detailed review. Keep subscriptions to chat tools separate from usage-based developer services: ChatGPT Plus or Pro and Claude Pro or Max do not include API calls. Existing automations may therefore have separate credentials, owners and bills to check.
Write a short handover that staff can actually follow
The most useful handover fits on one page. It names the approved workspace, describes allowed work, lists excluded information, explains where finished documents belong and identifies the person to contact when access breaks. It should make the desired behaviour easy to follow on a busy day.
Illustrative staff wording: Use the company AI workspace for approved drafting tasks. Check the workspace name before adding material. Use the current service reference document. Do not enter payment details, private health information or another client's files. Review every customer-facing answer and save the final version in the normal business folder. Report unexpected access or incorrect content to the manager.
Ask each person to show the process rather than simply confirm that they have read it. A two-minute demonstration can reveal a wrong account, an inaccessible source file or a forgotten approval step. Fix the specific obstacle and repeat the task with fictional data.
Do not tell staff that administrators can always read everything, or that their work is invisible to the company. Visibility varies by product, plan and feature. On Claude Team, for instance, the Primary Owner can export the organisation's data, including members' chats, so “private” chats in a company workspace are not private from the business. Explain the controls your business has actually confirmed, and give staff a plain description of the workplace monitoring and data arrangements that apply.
Test a departure before the first real departure
Use an authorised test member or a carefully agreed test with a colleague. Confirm that the business can preserve the required shared work, remove membership and check access again. Inspect connected services separately. Removing a person from an AI workspace does not prove that every external connection or downloaded file has disappeared.
An illustrative yoga studio removes a departing manager from the AI member list but forgets that an automated report uses a separate connection the manager created. The report later stops. The fix is to inventory that dependency before departure, give the workflow an approved replacement owner and test it, then revoke the obsolete access.
Record the departure checks with a date and responsible person: shared business assets accessible, workspace access removed, connected services reviewed, recovery ownership current and billing reviewed. The AI offboarding checklist expands this into a repeatable routine.
Finish the migration only when every intended user can complete the sample task, the backup administrator can perform their assigned duties, and essential business files remain accessible without the original user's login. Review the account register when someone joins, changes role or leaves. Those checks turn a new subscription into an account setup the business can actually control.
Further reads
- How to Set Up Single Sign-On for Your Team's AI Tools — Decide whether central sign-in would help your team.
- How to Use ChatGPT Projects to Keep Client Work Separate — Arrange client context after the workspace is ready.
- How to Set Up Claude Projects as a Shared Team Assistant — Prepare shared instructions if your team chooses Claude.
- How to Set Spending Limits and Alerts on Pay-As-You-Go AI Tools — Control separate usage-based AI spending.
- AI Security Checklist Before Connecting Tools to Email and Files — Review access before connecting business email or files.
- What to Check in an AI Tool's Privacy Policy and Terms — Seven checks for any AI tool's privacy policy and terms, the words to search for, and how ChatGPT, Claude, Gemini and Copilot compare.
- Who in Your Team Actually Needs a Paid AI Licence? — A three-question test for deciding who gets a paid AI seat, a two-week usage log, and a florist's before-and-after seat bill with 2026 list prices.
- How to Stop AI Tools Training on Your Business Data — The exact training switches in ChatGPT, Claude, Gemini, Copilot and Perplexity, plus the hidden AI features most owners forget to check.
- How to Onboard New Hires Onto Your AI Tools and Rules — A first-month plan for new starters on your AI tools: accounts before day one, one-page rules, buddy-checked tasks and a sign-off for wider access.
- AI Acceptable Use Policy for a Small Professional Firm — A clause-by-clause checklist and one-page sample policy for accountants, lawyers and consultants who handle confidential client work.
- How to Redact Personal Data From Documents With AI Before Sharing — AI is good at finding personal data in documents and bad at removing it. A detect, review, redact and verify routine for files you share outside.
- How to Keep Customer Data Private When Your Team Uses AI — Eight steps to keep customer details out of the wrong AI tools, with a filled-in data table, redaction examples, policy wording and a quarterly audit.
- ChatGPT Plus vs ChatGPT Business: Which Plan Does a Team Need? — What ChatGPT Business adds over Plus for a team, what it costs per seat, when Plus is still fine, and how to move existing chats across without losing work.
- Is Claude Team Worth It for a Small Business? — When Claude Team earns its $20-$25 a seat over separate Pro accounts, three businesses that get different answers, and how to make a shared project pay.
- Which AI Is Best for a Small Business? — Choose an AI assistant through a practical task trial, with realistic prompts, cost checks and examples from service businesses.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: OpenAI, ChatGPT Business pricing and ChatGPT Learn, User lifecycle management and Roles and workspace permissions; Anthropic, Claude Team pricing and Team plan help pages (all checked September 2026). Account registers, timings and business scenarios are illustrative.