ChatGPT Business Setup Guide (2026): How to Set Up a Workspace for a Small Team, Step by Step

TL;DR: how to set up ChatGPT Business

As of September 2026, setting up ChatGPT Business for a small team takes about one focused hour for the owner and one week to roll out. Buy at least two seats ($20 per user per month billed annually for Standard), set two owners, verify your domain and turn on SSO, invite people with the right seat type, and build one shared project that holds your business context. Don't build new custom GPTs: OpenAI says it plans to retire them, with December 11, 2026 as the published Enterprise retirement date. Every setting below comes from OpenAI's help center, read on September 12, 2026.

Most ChatGPT setup videos on page one were recorded when the plan was still called Team. The plan was renamed Business on August 29, 2025, and the seats, the app directory, and the GPT story have all changed since. Here's the order that works now.

Before you start: have these five things ready

• The owner's work email. Whoever signs up becomes the workspace owner.
• A second owner. Your ops person, your business partner, anyone who isn't going on vacation the same week as you.
• DNS access for your domain if you want SSO. You'll need to add a verification record.
• A card. Self-serve Business is paid by card. If you need invoices, purchase orders, or net terms, OpenAI says that's a contracted offering, not self-serve Business.
• Three recurring jobs your team already does every week. You'll build the first project around them.

Step 1: Pick seats (Standard, Premium, or a mix)

A ChatGPT Business workspace needs at least two paid seats: two Standard, two Premium, or one of each. Both types count toward a 200-seat limit.

The math for a five-person team: five Standard seats on annual billing is $100 a month. Swap one of them for Premium and it's $180. Start everyone on Standard. After 30 days you'll know who actually hits the wall, and you can move just that person. The full seat breakdown, including what forces Enterprise, is on ChatGPT Business pricing.

One billing note: new seats are charged immediately, prorated. Buy what you need today, not what you hope to need in March.

Step 2: Create the workspace and give it a real name

Sign up and you get the owner role automatically. Two things to do in the first five minutes:

1. Rename the workspace. Until you do, new people see a generic workspace name when they join, and "which one is ours?" becomes your first support ticket.
2. Decide on workspace discovery. It's on by default for Business. Anyone who signs up with a verified email on your domain can see the workspace and request to join. You can also turn on automatic approval, but that doesn't buy a seat. If none are free, the request waits for an owner.

Step 3: Set roles before you invite anyone

ChatGPT Business separates roles (what someone can change) from seats (how much they can use). There are four roles:

• Owner: everything, including billing, invoices, seat types, role changes, identity and SSO, and GPT settings.
• Admin: removes users, manages groups and apps, sets spend controls, changes workspace settings.
• Analytics Viewer: sees workspace analytics, can't change anything.
• Member: uses ChatGPT fully and can invite other members, with no admin rights.

Only owners can switch someone's seat type or change a role. My rule for a small team: two owners, zero admins, everyone else a member. You can add an Analytics Viewer later if the person who cares about adoption shouldn't touch settings.

Step 4: Verify your domain and turn on SSO

SSO and domain verification are included with ChatGPT Business, with SAML and OpenID Connect supported. The owner does it in this order:

1. Open Workspace settings, Identity & access, Identity & provisioning.
2. Under Verified Domains, add your email domain and verify it. You can verify more than one.
3. Under Single Sign-On, choose SAML or OIDC and configure the app in your identity provider.
4. Assign one test user and confirm they can sign in before you require it for everyone.

What trips people up:

• No SCIM. A standalone Business plan doesn't include SCIM, synced groups, or automatic directory provisioning. Adding and removing people stays a manual job in ChatGPT.
• Existing accounts. Invite each person with the email already on their OpenAI account. OpenAI says a different identity-provider email can create a separate account, and suddenly their chat history "disappeared."
• Contractors. People on another domain need the owner to turn on Allow External Domain Invites first.
• Lockouts. Before you require SSO, confirm a second owner or recovery method exists.

Step 5: Invite the team with the right seat type

Go to Workspace settings, Members, Invite member. For more than a handful of people, upload a CSV with three columns: email,role,seat type. A row like sam@yourco.com,member,standard is all it takes.

Two things OpenAI's docs say that surprise owners. First, sending an invitation doesn't purchase or reserve a seat. Availability is checked when the person accepts, so buy seats before you send the email. Second, people who already pay for Plus can keep their personal workspace separate from the Business one or merge them, and you can't force either choice. Tell them which to use for company work, in writing.

Step 6: Build one shared project, not a pile of chats

This is the step that decides whether ChatGPT sounds like your business or like everyone else's. On Business, a project holds up to 40 files (10 per upload), its own instructions, and every chat inside it. You can share it with individuals, groups, or the whole workspace by link, and up to 100 people can join a workspace project.

Build one project called something like "How we do business." Put in your offers and prices, your top 20 customer questions with the answers you actually give, three emails that sound like you, and your "never say this" list. Give most people chat access and two people edit access. Anyone joining by workspace link gets chat access by default.

Know the tradeoffs before you share it:

• A shared project switches to project-only memory and can't be switched back. It won't see anyone's personal memories.
• OpenAI says ChatGPT Work isn't available in a project set to project-only memory.
• Deleting a file in a shared project removes it for everyone. Deleting the project deletes everyone's chats in it.

If you're weighing a project against a custom GPT for this, read ChatGPT Projects vs custom GPTs first. Short version: the project wins.

Step 7: Don't build new custom GPTs (OpenAI is retiring them)

Business members can still create GPTs today. I'd skip it. OpenAI's help center now says it's "planning to retire custom GPTs" and recommends moving workflows to plugins. The published timeline for Enterprise workspaces:

• September 17, 2026: target date for the migration tool and banner.
• September 25, 2026 (planned): creation of new custom GPTs ends.
• December 11, 2026: retirement. Custom GPTs stop running.

OpenAI says the change affects all ChatGPT plans and that other plans may follow the same timeline, with notices in the product. Building a new GPT for a fresh workspace this month is building on a dated floor. If an older GPT already runs a real job for you, write down its instructions, files, and any custom actions now. OpenAI says instructions carry over as a skill, but custom actions don't transfer at all.

Step 8: Connect apps and install Company Knowledge

On July 9, 2026, OpenAI moved its app directory into a Plugin directory. Apps are still the integrations that reach your Google Drive, Slack, or Microsoft 365. Plugins package apps with reusable instructions. In a Business workspace, apps are enabled by default.

Company Knowledge is the one to turn on first. It's a plugin on Business, Enterprise, and Edu that answers questions from your connected sources. An owner or admin opens Admin, Plugins, picks Company Knowledge, and sets the installation policy to Installed. People then type @Company Knowledge or pick it from the + menu. It only returns what each person can already see in the connected app, so the intern doesn't get the payroll folder.

Two settings worth a look while you're there:

• App permissions. The default, "Important actions," lets ChatGPT read from apps automatically and asks before anything that sends, deletes, buys, or shares. Admins can restrict what each app is allowed to do. For a small team, leave the default and don't hand out "allow all actions."
• Fewer apps, not more. Connect the two or three places your files and conversations actually live. Every extra app is another place ChatGPT searches and another permission to review.

Step 9: Lock down data rules and spend

The defaults are better than most owners assume. OpenAI says it doesn't train on Business data by default, encrypts it with AES-256 at rest and TLS 1.2 or higher in transit, and keeps chats until someone deletes them, after which they're removed from its systems within 30 days. Files uploaded to a project stay until the project is deleted.

What the defaults don't cover:

• Health data. Self-serve Business doesn't come with a BAA. If anyone on your team touches patient information, read is ChatGPT HIPAA compliant before they paste anything.
• Data residency. OpenAI's residency list names Enterprise, Edu, Healthcare, and API customers. Business isn't on it.
• Your own rules. The software can't know that client contracts stay out. Write a one-page AI acceptable use policy before the invite goes out, not after the first incident.

For spend: owners buy optional workspace credits under Workspace settings, Billing, and those credits are valid for 12 months. Set Usage Alerts in the same place on day one, and leave automatic recharge off until you've seen a month of real usage.

Step 10: Run a one-week rollout

1. Monday: the owner does steps 1 through 4. About an hour, most of it waiting on DNS.
2. Tuesday: invites go out with the one-page policy and a 30-minute kickoff call. Show the shared project live.
3. Wednesday: everyone moves one real piece of work into the project. Not a test prompt, a real email or proposal.
4. Thursday: each person picks one of your three recurring jobs and runs it through ChatGPT start to finish.
5. Friday: 20-minute review. What worked, what the project got wrong, what to add to its files. Fix the project, not the people.

At day 30, check workspace analytics and who ran into limits. That's when Premium seats and credits get decided, with data instead of guesses. The meters that actually run out are explained on ChatGPT usage limits.

The mistakes I see in week two

• Paying for people who left. Removing a member ends their access but doesn't remove the seat from billing. An owner has to remove the seat under Members, Users, Manage seats.
• One owner. OpenAI's own SSO guide says to transfer ownership before the only owner leaves. Have two from day one.
• Company work in personal accounts. If people keep using their personal workspace, the no-training default and your admin controls don't cover that work.
• Twelve GPTs, zero projects. See step 7. Ship one good project instead.
• Connecting everything. More apps doesn't mean better answers. It means more places to search and more permissions to audit.

Want it done for you?

Everything above is doable in-house, and plenty of teams should do it themselves. If you'd rather hand it off, the ChatGPT Business setup is my done-for-you version: workspace and SSO configured with your owner, apps and Company Knowledge connected, the shared business-context project built, one workflow pack, and team training. From $4,500, about two weeks.