ChatGPT Team Invite: Add Members to the Right Workspace
Invite colleagues with the correct email, confirm their workspace access, and give them a clear first task. Keep the onboarding record separate from the invitation.
Updated 5 min read
To send a ChatGPT Team invite, open the intended workspace, go to Workspace settings, choose Members, and select Invite member. Enter the colleague’s exact email address, review the access being offered, and send the invitation. OpenAI now calls the former Team plan Business (opens in a new tab), so that is the name you should expect in current instructions.
An invitation gets someone through the door; it does not explain the job waiting inside. Tools like fenbs can hold the shared onboarding tasks, project decisions, and next steps that a new teammate needs after access is confirmed.
How do you send the invitation?
- Select the company workspace before opening its settings. Compare the name with the workspace your colleagues already use.
- Open Workspace settings, then Members, and choose Invite member. Enter email addresses manually or use the bulk-import option when appropriate.
- Review the proposed role and seat type. Ask an owner to handle changes that your own role cannot make.
- Send the invitation and tell the colleague which workspace name to look for. Use your normal company channel to confirm that the invitation was expected.
- Have the colleague accept with the invited email address, then confirm that they can select the intended workspace.
These are the basic steps in OpenAI’s member-management guide (opens in a new tab). Start with one colleague before inviting a large group. A small test catches a misspelled address, an unclear workspace name, or a misunderstood role before the same issue reaches everyone.
What should you check before adding a colleague?
Confirm who the person is joining as, which address they use for work, and whether they are an intended ongoing member of the organization. A forwarded email is not a substitute for checking identity. Ask the person to confirm the address directly rather than guessing from an old contact list.
Check capacity with the workspace owner. Sending an invitation does not reserve or purchase a seat; availability is checked when the recipient accepts. Keep current membership requirements behind OpenAI’s guide rather than building a permanent onboarding document around a number that may change.
You also need a named person who can answer onboarding questions. Write down who sends invitations, who approves spending, and who verifies the first successful sign-in. Our guide to apps for teams places those responsibilities in the wider company tool setup.
What should the invited person do next?
Tell the recipient to use the same email address that received the invitation. OpenAI’s employee-onboarding guidance (opens in a new tab) distinguishes signing into an account from joining a workspace. Someone who already uses ChatGPT should check their account identity before proceeding.
Give them the company workspace name and the approved sign-in method in a short message. If company single sign-on is required, that means using the organization’s sign-in service. Explain the term once instead of assuming a new employee knows which button or company account you mean.
Joining the workspace and moving personal content are separate choices. If a migration prompt appears, pause long enough to understand what it changes. Follow the current OpenAI guidance and your company’s instructions; clicking through an unfamiliar prompt is a poor first onboarding task.
How do you track pending invitations and later changes?
Use the Members area to distinguish pending invitations from people who have joined. Admins and owners can manage pending invitations, including resending where available. Ask an owner to review a role or seat-type change rather than repeatedly sending another invitation.
Keep a simple progress record alongside that administrative view: invitation sent, acceptance confirmed, first task checked, and any question waiting on someone. Those are different milestones. A sent email is evidence of an attempt, while opening the correct workspace is evidence that the new colleague can begin.
For example, a design studio might record that its new researcher can enter the workspace but still needs the approved project brief. The remaining job is then clear. In fenbs, shared tasks and project context keep that handoff visible without treating invitation status as the whole onboarding process.
What should someone learn after access works?
Give the new member one small, real task. Ask them to identify the project goal, find the current approved source, draft a short result, and name the person who reviews it. This tests whether they understand the work, rather than whether they can simply produce a response.
- The current project: its goal, source material, and the next useful contribution.
- The decisions: what people already approved and which questions remain open.
- The boundaries: what information may be used and which actions need human approval.
- The handoff: where to save reviewed results and how to describe unfinished work.
Keep the same onboarding standard when colleagues prefer different assistants. The Claude versus ChatGPT guide covers the broader choice; membership in one workspace should not become the only place the team records what it agreed.
Give new members a project they can pick up
Put the onboarding tasks, approved project decisions, and remaining questions in fenbs. A teammate can read the work record, and a connected assistant can start with the same context. Confirm access in ChatGPT, then keep the next useful action with the project.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account. One person can start free, with no credit card, before setting up shared work on a team kanban board.
- Add the project and create the tasks needed to bring the new colleague into the work. Include the goal, the next step, and what will show that each task is finished.
- Record the onboarding rules people agreed in Decisions and rules. Keep a proposed policy open until a person decides it.
- Use the integration guides to connect a supported assistant. Ask it to read the project context before helping with the first task.
- Save progress when the session ends. Record what was checked, what remains, and which question needs a person next.
fenbs does not send ChatGPT invitations or repair workspace membership. If your only requirement is adding a person to ChatGPT, its own member controls are the right fit. Use fenbs when the onboarding work needs a shared home beyond that access screen.
How can you tell the onboarding is complete?
Ask the colleague to confirm the workspace name and explain their first task in their own words. Then check a small piece of work together. Completion means the person knows where to start and how to get a decision reviewed, as well as being able to sign in.
For invitation failures, use the focused invite troubleshooting guide. For the surrounding subscription, consult the ChatGPT Team plan guide; for collaboration beyond the access step, browse the shared team brain guides.