Set up and manage @ChatGPT in Slack and Microsoft Teams

In supported Slack and Microsoft Teams conversations, people can ask @ChatGPT to summarize information, draft responses, or use approved tools.

For everyday use, see the Help Center user guide.

ChatGPT admins connect platforms and configure surfaces, plugins, and workspace connections. Slack and Teams admins manage the messaging-platform setup.

For detailed setup, see the Help Center setup guide.

How access works

Choose which plugins and workspace connections @ChatGPT’s service account can use. People who can use the surface can access those tools and data, which may differ from their personal access.

@ChatGPT uses configured connections and conversation context. It does not inherit a person’s file, app, or private-channel access. Personal plugin access requires separate authorization where supported. Shared replies are visible to conversation participants.

Before you begin

Before setup, identify the ChatGPT workspace and Slack workspaces or Microsoft Teams tenant you intend to connect. Confirm that @ChatGPT is available for your organization and agree on the pilot audience.

Assign the following responsibilities before setup:

• ChatGPT workspace admin or owner: Connect the platform, create the surface, and choose its plugins and workspace connections.

• Slack or Teams admin: Approve permissions and install the app. Teams admins also manage audience assignment and coordinate required consent with an authorized Microsoft administrator.

• Connection owner: Prepare approved company accounts and verify their resource and action permissions. Follow the Workspace connections guide for authorization.

• Pilot owner: Define the audience and supported conversations to test, including people who should not have access.

Set up Slack

1. Plan your surface configuration

A surface defines where @ChatGPT is available and which tools it can use.

Configure one surface per Slack workspace, including each connected workspace in Enterprise Grid.

2. Connect Slack in ChatGPT

In the OpenAI admin console, select the intended workspace and open Agents to connect Slack. Review the requested permissions.

Have the Slack owner or authorized app manager complete any required approval, then confirm the connection in ChatGPT.

If your organization already uses ChatGPT in Slack, a Slack admin must approve the additional app permissions to use the new @ChatGPT experience. See the guidance for existing Slack installations. Existing installations won’t stop working immediately at launch.

3. Create the surface and choose its scope

Create a surface for the connected Slack workspace and give it a recognizable name.

For a channel pilot, choose Selected channels only and add the approved channels. This does not block direct messages.

4. Test the experience

Before adding company connections, test a request in an approved Slack channel and in a direct message.

If @ChatGPT does not respond or show that it is working within a minute, follow the setup troubleshooting checks below.

Set up Microsoft Teams

Microsoft Teams admins manage app installation, user access, and any required Microsoft consent. ChatGPT workspace admins manage the Teams connection, surface settings, and workspace connections.

For step-by-step setup instructions, see the Help Center setup guide.

Check your surface scope

Confirm the surface matches its Slack workspace or Teams tenant. Enterprise Grid needs one surface per connected workspace.

Configure company access

Keep company-managed access separate from personal authorization:

1. Personal access: Where supported, using plugins connected in ChatGPT.com or the desktop app requires separate authorization. This is separate from shared company access.

2. Shared company access: Surface plugins use the configured company account’s permissions, which may differ from participants’ personal access. Members do not each authenticate the shared account.

1. Check the surface’s connected Slack workspace or Teams tenant.

2. Have the connection owner verify the approved company account’s permissions. Use the Workspace connections guide for setup and authorization.

3. Add the approved plugin and select the intended workspace connection.

4. Save, then have the pilot owner test the connection in its Slack or Teams conversation.

Enable Codex Cloud for Slack

Codex Cloud delegation from Slack requires separate setup where available.

1. Enable Codex Cloud for your workspace.

2. Where Codex Cloud role-based access control applies, grant access to the Slack surface’s service account and requesting users.

3. Publish a cloud environment and share it with your workspace.

4. Verify each requesting user’s access to the environment and any repositories requiring authentication.

5. Have a pilot user request a repository investigation in Slack and confirm the coding task starts.

The service account finds environments; the coding task runs as the requesting user. The service account does not need GitHub access.

Validate setup

Before expanding access, use approved test data to check successful requests and access boundaries for each supported conversation type.

• Slack: Test an approved channel, an excluded channel, and direct messages. Channel restrictions do not block direct messages.

• Teams: Test assigned and unassigned users. Test personal chat only where your surface supports it.

• Connections and actions: Verify the acting account, source access, and results of enabled write or send actions in approved destinations.

• Reply visibility: Confirm who can see responses and open linked sources or files.

Maintain the surface

Assign an owner to maintain platform connections, app assignment, and approved plugins. Involve platform admins for installation or consent changes and connection owners for reauthorization.

After a permission or connection change, repeat the relevant validation checks before expanding access. Use the Workspace connections guide to review company-account access and troubleshoot authorization.

Before offboarding or removing access, identify affected surfaces and connections and coordinate with their administrators.

Setup FAQ