
Setting up ChatGPT for a company means creating a ChatGPT Business workspace (formerly ChatGPT Team), verifying your email domain, assigning owner and admin roles, putting billing on a company card, and reviewing the data, sharing and app settings before you invite staff. The workspace itself takes under an hour. The decisions around it take longer, and skipping them is how companies end up with a workspace nobody owns and apps nobody approved. This checklist covers both, following OpenAI's help pages as of October 2026.
If you have not chosen a plan yet, ChatGPT Business vs Plus and Pro explains why a workspace rather than personal seats; the costs are in ChatGPT Business pricing.
Before you start: owners, domain and user inventory
Settle four things before the workspace exists.
- Workspace owners. One named person and a backup, both on company email addresses rather than a contractor's or a founder's personal address. Owners hold billing, identity settings and the ability to remove anyone, so two is the minimum for recovery.
- Domain. The email domain staff use, and who controls its DNS. Domain verification needs a TXT record, so find the registrar login now.
- User inventory. Who gets a seat in the first wave, who already uses a personal ChatGPT account for work and on which email, and which projects or GPTs they would want to keep. That list sets the seat count, the migration plan and the training schedule.
- Approved data and pilot tasks. A short written statement of what staff may put into ChatGPT, what they may not, and the three to five tasks the pilot will measure. Our one-page AI usage policy template is enough for most companies.
How do you set up a ChatGPT Business workspace, step by step?
- Create the workspace. OpenAI's sign-up article: open the Business sign-up page, sign in with the owner's company account, choose Business, choose at least two Standard or Premium seats and monthly or annual billing, pay by card and invite teammates. The creator becomes the owner. Invite the second owner immediately.
- Set billing. Under Workspace settings, Billing shows seats, the next charge, invoices, payment method, billing schedule, credits, auto-reload, usage alerts and the default seat type. Agree how finance gets the invoices and set the default seat type to Standard. You pay for every seat bought, assigned or not, so buy for the first wave and add seats as people join.
- Verify the domain. Under Identity and access, add the DNS TXT record OpenAI gives you (host name @) and click Check Domain. OpenAI's domain verification article says propagation can take up to 24 hours, the check must be completed within a seven-day window, a parent domain does not verify its subdomains, and a domain can generally be verified for only one tenant. A Business workspace can verify more than one domain.
- Decide identity. Business includes SAML and OIDC single sign-on. Decide whether to enable it before or after the pilot, and in the meantime ask every user to turn on MFA with an authenticator app or passkey, because OpenAI says MFA cannot be enforced at the workspace level. Review workspace discovery (on by default in Business, letting anyone with a verified-domain email find and request to join), whether to auto-accept those requests, whether to enable automatic account creation, which OpenAI says adds eligible members after they sign in with a verified-domain email (plan seats for everyone it could admit), and whether to allow external-domain invites for contractors. The identity steps are in ChatGPT SSO setup for Business and Enterprise.
- Assign roles. OpenAI's roles article defines four: Owner (billing, identity, workspace configuration, can invite other owners), Admin (manage users and routine administration), Analytics Viewer and Member. Only owners can switch seat types, invite admins or owners, change roles, view invoices and manage identity and GPT settings. Two owners, one or two admins, everyone else a Member. Note that members can invite other members and OpenAI says this cannot currently be restricted, so the usage policy has to say who may.
- Set data controls. Training on workspace data is off by default. Decide Memory: individuals can disable it, and an owner can turn it off for the whole workspace, which deletes existing memories. Set and record the retention choice; deleted or unsaved conversations are removed within 30 days. Shared links already stay inside the workspace and cannot be disabled on Business. Review GPT settings under Workspace settings. The full list is in our ChatGPT Business security settings checklist.
- Review apps and plugins. In Business, connected apps are enabled by default. Go through the Plugins page, disable anything the policy does not allow, and set the approval default to Always ask or Allow read actions rather than Allow all actions. Microsoft apps (SharePoint, Outlook, Teams) need a Microsoft Entra administrator to consent to the ChatGPT application before their actions work. Only admins and owners can publish custom MCP servers in Business; keep it that way.
- Invite the pilot group. Under Workspace settings, Members, Invite member: enter emails or upload a CSV with the columns email, role and seat type. Invite each person with the exact email already on any personal ChatGPT account; OpenAI's onboarding article warns that a different address creates a separate account and makes history appear missing. An invitation does not reserve a seat; availability is checked when it is accepted.
- Build the first shared assets. One shared project or workspace agent per pilot task, each with a named owner. Prefer projects and agents over custom GPTs for anything new: OpenAI has scheduled custom GPTs to retire on December 11, 2026 in favor of plugins. Workspace agents default write actions to Always ask; leave that in place.
- Run the pilot, then the acceptance checks below, then invite everyone.
Which settings should be decided in the first week?
| Setting | Default in ChatGPT Business | Decide | Owner |
|---|---|---|---|
| Workspace discovery | On | Keep on with auto-accept if only staff use the domain; off if contractors or a parent company share it | Workspace owner |
| Automatic account creation | Adds eligible verified-domain users after they sign in | On only if every verified-domain user should get a seat | Workspace owner |
| External-domain invites | Setting under Identity and access | Off unless named contractors need seats | Workspace owner |
| Members inviting members | Allowed; cannot be restricted | Write the rule into the usage policy | Workspace owner |
| Apps and plugins | Enabled | Disable unapproved apps; approval default Always ask or read-only | Admin |
| Memory | Available; users can disable it | Follow the data policy; turning it off workspace-wide deletes existing memories | Workspace owner |
| Spend limits and alerts | No limits specified | Monthly credit limits per seat type, usage alerts, decide on auto-reload | Workspace owner |
| Default seat type | Set in Billing | Standard; Premium for named heavy users | Workspace owner |
| SSO | Available, not configured | Configure and pilot, then roll out to all | Workspace owner and identity admin |
| GPT and agent sharing | Every role can create a GPT | Share inside the workspace only; one owner per shared asset | Workspace owner |
| Retention | Admin-controlled | Set it and record the reason | Workspace owner |
How should employees be onboarded?
Invite the pilot group first, not the whole company. Ten to fifteen people across two or three departments is enough to find the settings you got wrong. Each person gets a seat, the one-page usage policy, the pilot tasks for their role and one shared project or agent built for one of those tasks, so the first session starts with a task rather than a blank prompt box. Hold a 45-minute working session per group around their own documents, collect what failed, and invite the rest of the company once the pilot settings are confirmed. Our AI training for employees runs these sessions by role.
Staff who already use a personal account decide, after joining, whether to keep that personal workspace separate or merge it into the company workspace. The merge is permanent, and OpenAI says Business admins cannot require it. The decision rule and the owner-led steps are in moving personal ChatGPT use into a company workspace.
What are the acceptance checks before launch?
- Two owners on company accounts can sign in, and the recovery path for a lost owner account is written down.
- The domain shows as verified under Identity and access.
- Every first-wave seat is assigned to a named person; none belongs to a shared mailbox.
- Memory, retention, discovery and app settings match the written decision for each, with a screenshot filed.
- Each enabled app was tested with a low-privilege account to confirm it returns only what that account can already see.
- Shared projects and agents have a named owner and workspace-only sharing.
- If SSO is in scope, the pilot group has signed in through it and the fallback owner account has been tested.
- Billing is on a company card, finance knows how to get the invoices, and spend limits are set.
- The leaver procedure was rehearsed on a test user: removal, what happened to their projects, and the scheduled seat reduction.
Who owns the workspace after launch?
A workspace needs a standing owner for four recurring jobs: adding and removing people as staff change, reviewing new apps and shared agents before they spread, reading the usage report for idle seats and runaway credits, and re-checking settings when OpenAI ships a feature. Name the person and put a 30-minute monthly review on the calendar; otherwise the workspace drifts back to the defaults within a quarter.
Frequently asked questions
How do I create a ChatGPT workspace for my company?
Sign in with the owner's company account on OpenAI's Business sign-up page, choose Business, buy at least two seats, pick monthly or annual billing, pay by card and invite the first members. The person who creates it is the owner.
Do we need to verify our domain?
Not to create the workspace, but yes for SSO, automatic account creation and workspace discovery, and it is the only way to tie the workspace to company identities. It is one DNS TXT record and a check within seven days.
What roles exist in ChatGPT Business?
Owner, Admin, Analytics Viewer and Member. Owners hold billing, identity, seat types and GPT settings; admins manage members and routine settings; members use ChatGPT and can create GPTs but have no admin rights.
Can employees bring their existing ChatGPT accounts into the workspace?
Yes. Invite them with the same email as the existing account. After joining, each person chooses whether to keep their personal workspace separate or merge it; the merge moves their own chats, files, GPTs and projects into the company workspace and cannot be undone.
How long does ChatGPT Business setup take?
The workspace takes minutes, domain verification up to 24 hours, and an SSO pilot a few days. A rollout with migration and training is measured in weeks, mostly waiting on decisions and calendars.
Do we need SSO on day one?
No. Business includes it, but a pilot can run on passwords with MFA turned on by each user. Enable SSO once the pilot works, because it is the only way to enforce MFA and to cut access the moment an identity-provider account is disabled.
Is setting up ChatGPT Enterprise different?
The order is similar but runs through OpenAI's Admin Console, with SSO and SCIM configured before broad onboarding and role-based access added. The plan comparison is in ChatGPT Business vs Enterprise.
How NetSys runs the rollout
Under our ChatGPT Business setup service, a NetSys engineer works through this checklist with your workspace owner: the plan decision, workspace creation, domain verification, roles, billing, data controls, apps and the first-week settings, each recorded with the reason it was chosen. Staff training is delivered through our AI training for employees, built around the pilot tasks your team picked. After launch, managed AI services covers joiners and leavers, app and agent reviews and the monthly usage report.
If you want the workspace set up, documented and handed over by an engineer, have NetSys manage the rollout.
Discuss chatgpt business setup for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.



