enterprise/admin-setup diff

enterprise/admin-setup.md +298 −86

Details

1# Admin Setup1# Admin Setup

2 2

3![Codex enterprise admin toggle](/images/codex/codex_enterprise_admin.png)

3This guide is for ChatGPT Enterprise admins who want to set up Codex for their workspace.5This guide is for ChatGPT Enterprise admins who want to set up Codex for their workspace.

4 6

7Use this page as the step-by-step rollout guide. For detailed policy, configuration, and monitoring details, use the linked pages: [Authentication](https://developers.openai.com/codex/auth), [Agent approvals & security](https://developers.openai.com/codex/agent-approvals-security), [Managed configuration](https://developers.openai.com/codex/enterprise/managed-configuration), and [Governance](https://developers.openai.com/codex/enterprise/governance).

5## Enterprise-grade security and privacy9## Enterprise-grade security and privacy

6 10

7Codex supports ChatGPT Enterprise security features, including:11Codex supports ChatGPT Enterprise security features, including:

8 12

9- No training on enterprise data13- No training on enterprise data

~~10- Zero data retention for the CLI and IDE~~14- Zero data retention for the App, CLI, and IDE (code stays in the developer environment)

~~11- Residency and retention follow ChatGPT Enterprise policies~~15- Residency and retention that follow ChatGPT Enterprise policies

12- Granular user access controls16- Granular user access controls

~~13- Data encryption at rest (AES 256) and in transit (TLS 1.2+)~~17- Data encryption at rest (AES-256) and in transit (TLS 1.2+)

18- Audit logging via the ChatGPT Compliance API

14 19

~~15For more, see [Security](https://developers.openai.com/codex/security).~~20For security controls and runtime protections, see [Agent approvals & security](https://developers.openai.com/codex/agent-approvals-security). Refer to [Zero Data Retention (ZDR)](https://platform.openai.com/docs/guides/your-data#zero-data-retention) for more details.

16 21

~~17## Local vs. cloud setup~~22## Pre-requisites: Determine owners and rollout strategy

18 23

~~19Codex operates in two environments: local and cloud.~~24During your rollout, team members may support different aspects of integrating Codex into your organization. Ensure you have the following owners:

20 25

~~211. Local use includes the Codex app, CLI, and IDE extension. The agent runs on the developer’s computer in a sandbox.~~26- **ChatGPT Enterprise workspace owner:** required to configure Codex settings in your workspace.

222. Use in the cloud includes Codex cloud, iOS, Code Review, and tasks created by the [Slack integration](https://developers.openai.com/codex/integrations/slack). The agent runs remotely in a hosted container with your codebase.27- **Security owner:** determines agent permissions settings for Codex.

28- **Analytics owner:** integrates analytics and compliance APIs into your data pipelines.

23 29

~~24Use separate permissions and role-based access control (RBAC) to control access to local and cloud features. You can enable local, cloud, or both for all users or for specific groups.~~30Decide which Codex surfaces you will use:

25 31

~~26## Codex local setup~~32- **Codex local:** includes the Codex app, CLI, and IDE extension. The agent runs on the developer's computer in a sandbox.

33- **Codex cloud:** includes hosted Codex features (including Codex cloud, iOS, Code Review, and tasks created by the [Slack integration](https://developers.openai.com/codex/integrations/slack) or [Linear integration](https://developers.openai.com/codex/integrations/linear)). The agent runs remotely in a hosted container with your codebase.

34- **Both:** use local + cloud together.

27 35

~~28### Enable Codex app, CLI, and IDE extension in workspace settings~~36You can enable local, cloud, or both, and control access with workspace settings and role-based access control (RBAC).

29 37

30To enable Codex locally for workspace members, go to [Workspace Settings > Settings and Permissions](https://chatgpt.com/admin/settings). Turn on **Allow members to use Codex Local**. This setting doesn’t require the GitHub connector.38## Step 1: Enable Codex in your workspace

31 39

32After you turn this on, users can sign in to use the Codex app, CLI, and IDE extension with their ChatGPT account. If you turn off this setting, users who attempt to use the Codex app, CLI, or IDE will see the following error: “403 - Unauthorized. Contact your ChatGPT administrator for access.”40You configure access to Codex in ChatGPT Enterprise workspace settings.

33 41

~~34## Team Config~~42Go to [Workspace Settings > Settings and Permissions](https://chatgpt.com/admin/settings).

35 43

~~36Teams who want to standardize Codex across an organization can use Team Config to share defaults, rules, and skills without duplicating setup on every local configuration.~~44### Codex local

37 45

~~38| Type | Path | Use it to |~~46Codex local is enabled by default for new ChatGPT Enterprise workspaces. If

~~39| ------------------------------------ | ------------- | ---------------------------------------------------------------------------- |~~47 you are not a ChatGPT workspace owner, you can test whether you have access by

~~40| [Config basics](https://developers.openai.com/codex/config-basic) | `config.toml` | Set defaults for sandbox mode, approvals, model, reasoning effort, and more. |~~48 [installing Codex](https://developers.openai.com/codex/quickstart) and logging in with your work email.

~~41| [Rules](https://developers.openai.com/codex/rules) | `rules/` | Control which commands Codex can run outside the sandbox. |~~

~~42| [Skills](https://developers.openai.com/codex/skills) | `skills/` | Make shared skills available to your team. |~~

43 49

~~44For locations and precedence, see [Config basics](https://developers.openai.com/codex/config-basic#configuration-precedence).~~50Turn on **Allow members to use Codex Local**.

52This enables use of the Codex app, CLI, and IDE extension for allowed users.

54If this toggle is off, users who attempt to use the Codex app, CLI, or IDE will see the following error: “403 - Unauthorized. Contact your ChatGPT administrator for access.”

56#### Enable device code authentication for Codex CLI

45 57

~~46## Codex cloud setup~~58Allow developers to sign in with a device code when using Codex CLI in a non-interactive environment (for example, a remote development box). More details are in [authentication](https://developers.openai.com/codex/auth/).

60![Codex local toggle](/images/codex/enterprise/local-toggle-config.png)

62### Codex cloud

47 63

48### Prerequisites64### Prerequisites

49 65

57 73

58Start by turning on the ChatGPT GitHub Connector in the Codex section of [Workspace Settings > Settings and Permissions](https://chatgpt.com/admin/settings).74Start by turning on the ChatGPT GitHub Connector in the Codex section of [Workspace Settings > Settings and Permissions](https://chatgpt.com/admin/settings).

59 75

~~60To enable Codex cloud for your workspace, turn on **Allow members to use Codex cloud**.~~76To enable Codex cloud for your workspace, turn on **Allow members to use Codex cloud**. Once enabled, users can access Codex directly from the left-hand navigation panel in ChatGPT.

78Note that it may take up to 10 minutes for Codex to appear in ChatGPT.

80#### Enable Codex Slack app to post answers on task completion

82Codex posts its full answer back to Slack when the task completes. Otherwise, Codex posts only a link to the task.

84To learn more, see [Codex in Slack](https://developers.openai.com/codex/integrations/slack).

86#### Enable Codex agent to access the internet

88By default, Codex cloud agents have no internet access during runtime to help protect against security and safety risks like prompt injection.

90This setting lets users use an allowlist for common software dependency domains, add domains and trusted sites, and specify allowed HTTP methods.

61 91

~~62Once enabled, users can access Codex directly from the left-hand navigation panel in ChatGPT.~~92For security implications of internet access and runtime controls, see [Agent approvals & security](https://developers.openai.com/codex/agent-approvals-security).

63 93

64![Codex cloud toggle](/images/codex/enterprise/cloud-toggle-config.png)94![Codex cloud toggle](/images/codex/enterprise/cloud-toggle-config.png)

65 95

~~66After you turn on Codex in your Enterprise workspace settings, it may take up~~96## Step 2: Set up custom roles (RBAC)

~~67to 10 minutes for Codex to appear in ChatGPT.~~

68 97

~~69### Configure the GitHub Connector IP allow list~~98Use RBAC to control granular permissions for access Codex local and Codex cloud.

70 99

~~71To control which IP addresses can connect to your ChatGPT GitHub connector, configure these IP ranges:~~100![Codex cloud toggle](/images/codex/enterprise/rbac_custom_roles.png)

72 101

~~73- [ChatGPT egress IP ranges](https://openai.com/chatgpt-actions.json)~~102### What RBAC lets you do

~~74- [Codex container egress IP ranges](https://openai.com/chatgpt-agents.json)~~

75 103

~~76These IP ranges can change. Consider checking them automatically and updating your allow list based on the latest values.~~104Workspace Owners can use RBAC in ChatGPT admin settings to:

77 105

~~78### Allow members to administer Codex~~106- Set a default role for users who aren't assigned any custom role

107- Create custom roles with granular permissions

108- Assign one or more custom roles to Groups

109- Automatically sync users into Groups via SCIM

110- Manage roles centrally from the Custom Roles tab

79 111

~~80This toggle allows users to view Codex workspace analytics and manage environments (edit and delete).~~112Users can inherit more than one role, and permissions resolve to the most permissive (least restrictive) access across those roles.

81 113

~~82Codex supports role-based access (see [Role-based access (RBAC)](#role-based-access-rbac)), so you can turn on this toggle for a specific subset of users.~~114### Create a Codex Admin group

83 115

~~84### Enable Codex Slack app to post answers on task completion~~116Set up a dedicated "Codex Admin" group rather than granting Codex administration to a broad audience.

85 117

~~86Codex integrates with Slack. When a user mentions `@Codex` in Slack, Codex starts a cloud task, gets context from the Slack thread, and responds with a link to a PR to review in the thread.~~118The **Allow members to administer Codex** toggle grants the Codex Admin role. Codex Admins can:

87 119

88To allow the Slack app to post answers on task completion, turn on **Allow Codex Slack app to post answers on task completion**. When enabled, Codex posts its full answer back to Slack when the task completes. Otherwise, Codex posts only a link to the task.120- View Codex [workspace analytics](https://chatgpt.com/codex/settings/analytics)

121- Open the Codex [Policies page](https://chatgpt.com/codex/settings/policies) to manage cloud-managed `requirements.toml` policies

122- Assign those managed policies to user groups or configure a default fallback policy

123- Manage Codex cloud environments, including editing and deleting environments

89 124

~~90To learn more, see [Codex in Slack](https://developers.openai.com/codex/integrations/slack).~~125Use this role for the small set of admins who own Codex rollout, policy management, and governance. It's not required for general Codex users. You don't need Codex cloud to enable this toggle.

91 126

~~92### Enable Codex agent to access the internet~~127Recommended rollout pattern:

93 128

~~94By default, Codex cloud agents have no internet access during runtime to help protect against security and safety risks like prompt injection.~~129- Create a "Codex Users" group for people who should use Codex

130- Create a separate "Codex Admin" group for the smaller set of people who should manage Codex settings and policies

131- Assign the custom role with **Allow members to administer Codex** enabled only to the "Codex Admin" group

132- Keep membership in the "Codex Admin" group limited to workspace owners or designated platform, IT, and governance operators

133- If you use SCIM, back the "Codex Admin" group with your identity provider so membership changes are auditable and centrally managed

134

135This separation makes it easier to roll out Codex while keeping analytics, environment management, and policy deployment limited to trusted admins. For RBAC setup details and the full permission model, see the [OpenAI RBAC Help Center article](https://help.openai.com/en/articles/11750701-rbac).

136

137## Step 3: Configure Codex local requirements

138

139Codex Admins can deploy admin-enforced `requirements.toml` policies from the Codex [Policies page](https://chatgpt.com/codex/settings/policies).

140

141Use this page when you want to apply different local Codex constraints to different groups without distributing device-level files first. The managed policy uses the same `requirements.toml` format described in [Managed configuration](https://developers.openai.com/codex/enterprise/managed-configuration), so you can define allowed approval policies, sandbox modes, web search behavior, MCP server allowlists, feature pins, and restrictive command rules.

142

143![Codex policies and configurations page](/images/codex/enterprise/policies_and_configurations_page.png)

144

145Recommended setup:

146

1471. Create a baseline policy for most users, then create stricter or more permissive variants only where needed.

1482. Assign each managed policy to a specific user group, and configure a default fallback policy for everyone else.

1493. Order group rules with care. If a user matches more than one group-specific rule, the first matching rule applies.

1504. Treat each policy as a complete profile for that group. Codex doesn't fill missing fields from later matching group rules.

151

152These cloud-managed policies apply across Codex local surfaces when users sign in with ChatGPT, including the Codex app, CLI, and IDE extension.

153

154### Example requirements.toml policies

155

156Use cloud-managed `requirements.toml` policies to enforce the guardrails you want for each group. The snippets below are examples you can adapt, not required settings.

95 157

~~96As an admin, you can allow users to enable agent internet access in their environments. To enable it, turn on **Allow Codex agent to access the internet**.~~158![Example managed requirements policy](/images/codex/enterprise/example_policy.png)

159

160Example: limit web search, sandbox mode, and approvals for a standard local rollout:

161

162```toml

163allowed_web_search_modes = ["disabled", "cached"]

164allowed_sandbox_modes = ["workspace-write"]

165allowed_approval_policies = ["on-request"]

166```

167

168Example: add a restrictive command rule when you want admins to block or gate specific commands:

169

170```toml

171[rules]

172prefix_rules = [

173 { pattern = [{ token = "git" }, { any_of = ["push", "commit"] }], decision = "prompt", justification = "Require review before mutating remote history." },

174]

175```

176

177You can use either example on its own or combine them in a single managed policy for a group. For exact keys, precedence, and more examples, see [Managed configuration](https://developers.openai.com/codex/enterprise/managed-configuration) and [Agent approvals & security](https://developers.openai.com/codex/agent-approvals-security).

178

179### Checking user policies

180

181Use the policy lookup tools at the end of the workflow to confirm which managed policy applies to a user. You can check policy assignment by group or by entering a user email.

182

183![Policy lookup by group or user email](/images/codex/enterprise/policy_lookup.png)

184

185If you plan to restrict login method or workspace for local clients, see the admin-managed authentication restrictions in [Authentication](https://developers.openai.com/codex/auth).

186

187## Step 4: Standardize local configuration with Team Config

188

189Teams who want to standardize Codex across an organization can use Team Config to share defaults, rules, and skills without duplicating setup on every local configuration.

97 190

~~98When this setting is on, users can use an allow list for common software dependency domains, add more domains and trusted sites, and specify allowed HTTP methods.~~191You can check Team Config settings into the repository under the `.codex` directory. Codex automatically picks up Team Config settings when a user opens that repository.

192

193Start with Team Config for your highest-traffic repositories so teams get consistent behavior in the places they use Codex most.

194

195| Type | Path | Use it to |

196| ------------------------------------ | ------------- | ---------------------------------------------------------------------------- |

197| [Config basics](https://developers.openai.com/codex/config-basic) | `config.toml` | Set defaults for sandbox mode, approvals, model, reasoning effort, and more. |

198| [Rules](https://developers.openai.com/codex/rules) | `rules/` | Control which commands Codex can run outside the sandbox. |

199| [Skills](https://developers.openai.com/codex/skills) | `skills/` | Make shared skills available to your team. |

200

201For locations and precedence, see [Config basics](https://developers.openai.com/codex/config-basic#configuration-precedence).

202

203## Step 5: Configure Codex cloud usage (if enabled)

204

205This step covers repository and environment setup after you enable the Codex cloud workspace toggle.

206

207### Connect Codex cloud to repositories

208

2091. Navigate to [Codex](https://chatgpt.com/codex) and select **Get started**

2102. Select **Connect to GitHub** to install the ChatGPT GitHub Connector if you haven't already connected GitHub to ChatGPT

2113. Install or connect the ChatGPT GitHub Connector

2124. Choose an installation target for the ChatGPT Connector (typically your main organization)

2135. Allow the repositories you want to connect to Codex

214

215For GitHub Enterprise Managed Users (EMU), an organization owner must install

216 the Codex GitHub App for the organization before users can connect

217 repositories in Codex cloud.

218

219For more, see [Cloud environments](https://developers.openai.com/codex/cloud/environments).

220

221Codex uses short-lived, least-privilege GitHub App installation tokens for each operation and respects the user's existing GitHub repository permissions and branch protection rules.

222

223### Configure IP addresses

224

225If your GitHub organization controls the IP addresses that apps use to connect, make sure to include these [egress IP ranges](https://openai.com/chatgpt-agents.json).

226

227These IP ranges can change. Consider checking them automatically and updating your allow list based on the latest values.

99 228

100### Enable code review with Codex cloud229### Enable code review with Codex cloud

101 230

102To allow Codex to do code reviews, go to [Settings → Code review](https://chatgpt.com/codex/settings/code-review).231To allow Codex to perform code reviews on GitHub, go to [Settings → Code review](https://chatgpt.com/codex/settings/code-review).

232

233You can configure code review at the repository level. Users can also enable auto review for their PRs and choose when Codex automatically triggers a review. More details are on the [GitHub integration page](https://developers.openai.com/codex/integrations/github).

234

235Use the overview page to confirm your workspace has code review turned on and to see the available review controls.

236

237![Code review settings overview](/images/codex/enterprise/code_review_settings_overview.png)

238

239 Use the auto review settings to decide whether Codex should review pull

240 requests automatically for connected repositories.

241

242![Automatic code review settings](/images/codex/enterprise/auto_code_review_settings.png)

243

244 Use review triggers to control which pull request events should start a

245 Codex review.

246

247![Code review trigger settings](/images/codex/enterprise/review_triggers.png)

248

249### Configure Codex security

250

251Codex Security helps engineering and security teams find, confirm, and remediate likely vulnerabilities in connected GitHub repositories.

252

253At a high level, Codex Security:

254

255- scans connected repositories commit by commit

256- ranks likely findings and confirms them when possible

257- shows structured findings with evidence, criticality, and suggested remediation

258- lets teams refine a repository threat model to improve prioritization and review quality

259

260For setup, scan creation, findings review, and threat model guidance, see [Codex Security setup](https://developers.openai.com/codex/security/setup). For a product overview, see [Codex Security](https://developers.openai.com/codex/security).

261

262Integration docs are also available for [Slack](https://developers.openai.com/codex/integrations/slack), [GitHub](https://developers.openai.com/codex/integrations/github), and [Linear](https://developers.openai.com/codex/integrations/linear).

263

264## Step 6: Set up governance and observability

265

266Codex gives enterprise teams options for visibility into adoption and impact. Set up governance early so your team can track adoption, investigate issues, and support compliance workflows.

267

268### Codex governance typically uses

269

270- Analytics Dashboard for quick, self-serve visibility

271- Analytics API for programmatic reporting and business intelligence integration

272- Compliance API for audit and investigation workflows

273

274### Recommended baseline setup

275

276- Assign an owner for adoption reporting

277- Assign an owner for audit and compliance review

278- Define a review cadence

279- Decide what success looks like

280

281### Analytics API setup steps

282

283To set up the Analytics API key:

284

2851. Sign in to the [OpenAI API Platform Portal](https://platform.openai.com) as an owner or admin, and select the correct organization.

2862. Go to the [API keys page](https://platform.openai.com/settings/organization/api-keys).

2873. Create a new secret key dedicated to Codex Analytics, and give it a descriptive name such as Codex Analytics API.

2884. Select the appropriate project for your organization. If you only have one project, the default project is fine.

2895. Set the key permissions to Read only, since this API only retrieves analytics data.

2906. Copy the key value and store it securely, because you can only view it once.

2917. Email [support@openai.com](mailto:support@openai.com) to have that key scoped to `codex.enterprise.analytics.read` only. Wait for OpenAI to confirm your API key has Codex Analytics API access.

292

293![Codex analytics key creation](/images/codex/codex_analytics_key.png)

294

295To use the Analytics API key:

296

2971. Find your `workspace_id` in the [ChatGPT Admin console](https://chatgpt.com/admin) under Workspace details.

2982. Call the Analytics API at `https://api.chatgpt.com/v1/analytics/codex` using your Platform API key, and include your `workspace_id` in the path.

2993. Choose the endpoint you want to query:

300

301- /workspaces/`{workspace_id}`/usage

302- /workspaces/`{workspace_id}`/code_reviews

303- /workspaces/`{workspace_id}`/code_review_responses

304

3054. Set a reporting date range with `start_time` and `end_time` if needed.

3065. Retrieve the next page of results with `next_page` if the response spans more than one page.

103 307

104Users can specify whether they want Codex to review their pull requests. Users can also configure whether code review runs for all contributors to a repository.308Example curl command to retrieve workspace usage:

105 309

106Codex supports two types of code reviews:310```bash

311curl -H "Authorization: Bearer YOUR_PLATFORM_API_KEY" \

312 "https://api.chatgpt.com/v1/analytics/codex/workspaces/WORKSPACE_ID/usage"

313```

107 314

1081. Automatically triggered code reviews when a user opens a PR for review.315For more details on the Analytics API, see [Analytics API](https://developers.openai.com/codex/enterprise/governance#analytics-api).

1092. Reactive code reviews when a user mentions @Codex to look at issues. For example, “@Codex fix this CI error” or “@Codex address that feedback.”

110 316

111## Role-based access (RBAC)317### Compliance API setup steps

112 318

113Codex supports role-based access. RBAC is a security and permissions model used to control access to systems or resources based on a user’s role assignments.319To set up the Compliance API key:

114 320

115To enable RBAC for Codex, navigate to Settings & Permissions → Custom Roles in [ChatGPT’s admin page](https://chatgpt.com/admin/settings) and assign roles to groups created in the Groups tab.3211. Sign in to the [OpenAI API Platform Portal](https://platform.openai.com) as an owner or admin, and select the correct organization.

3222. Go to the [API keys page](https://platform.openai.com/settings/organization/api-keys).

3233. Create a new secret key dedicated to Compliance API and select the appropriate project for your organization. If you only have one project, the default project is fine.

3244. Choose All permissions.

3255. Copy the key value and store it securely, because you can only view it once.

3266. Send an email to [support@openai.com](mailto:support@openai.com) with:

116 327

117This simplifies permission management for Codex and improves security in your ChatGPT workspace. To learn more, see the [Help Center article](https://help.openai.com/en/articles/11750701-rbac).328- the last 4 digits of the API key

329- the key name

330- the created-by name

331- the scope needed: `read`, `delete`, or both

118 332

119## Set up your first Codex cloud environment3337. Wait for OpenAI to confirm your API key has Compliance API access.

120 334

1211. Go to Codex cloud and select **Get started**.335To use the Compliance API key:

1222. Select **Connect to GitHub** to install the ChatGPT GitHub Connector if you haven’t already connected GitHub to ChatGPT.

123 - Allow the ChatGPT Connector for your account.

124 - Choose an installation target for the ChatGPT Connector (typically your main organization).

125 - Allow the repositories you want to connect to Codex (a GitHub admin may need to approve this).

1263. Create your first environment by selecting the repository most relevant to your developers, then select **Create environment**.

127 - Add the email addresses of any environment collaborators to give them edit access.

1284. Start a few starter tasks (for example, writing tests, fixing bugs, or exploring code).

129 336

130You have now created your first environment. Users who connect to GitHub can create tasks using this environment. Users who have access to the repository can also push pull requests generated from their tasks.3371. Find your `workspace_id` in the [ChatGPT Admin console](https://chatgpt.com/admin) under Workspace details.

3382. Use the Compliance API at `https://api.chatgpt.com/v1/`

3393. Pass your Compliance API key in the Authorization header as a Bearer token.

3404. For Codex-related compliance data, use these endpoints:

131 341

132### Environment management342- /compliance/workspaces/`{workspace_id}`/logs

343- /compliance/workspaces/`{workspace_id}`/logs/`{log_file_id}`

344- /compliance/workspaces/`{workspace_id}`/codex_tasks

345- /compliance/workspaces/`{workspace_id}`/codex_environments

133 346

134As a ChatGPT workspace administrator, you can edit and delete Codex environments in your workspace.3475. For most Codex compliance integrations, start with the logs endpoint and request Codex event types such as CODEX_LOG or CODEX_SECURITY_LOG.

3486. Use /logs to list available Codex compliance log files, then /logs/`{log_file_id}` to download a specific file.

135 349

136### Connect more GitHub repositories with Codex cloud350Example curl command to list compliance log files:

137 351

1381. Select **Environments**, or open the environment selector and select **Manage Environments**.352```bash

1392. Select **Create Environment**.353curl -L -H "Authorization: Bearer YOUR_COMPLIANCE_API_KEY" \

1403. Select the repository you want to connect.354 "https://api.chatgpt.com/v1/compliance/workspaces/WORKSPACE_ID/logs?event_type=CODEX_LOG&after=2026-03-01T00:00:00Z"

1414. Enter a name and description.355```

1425. Select the environment visibility.

1436. Select **Create Environment**.

144 356

145Codex automatically optimizes your environment setup by reviewing your codebase. Avoid advanced environment configuration until you observe specific performance issues. For more, see [Codex cloud](https://developers.openai.com/codex/cloud).357Example curl command to list Codex tasks:

146 358

147### Share setup instructions with users359```bash

360curl -H "Authorization: Bearer YOUR_COMPLIANCE_API_KEY" \

361 "https://api.chatgpt.com/v1/compliance/workspaces/WORKSPACE_ID/codex_tasks"

362```

148 363

149You can share these steps with end users:364For more details on the Compliance API, see [Compliance API](https://developers.openai.com/codex/enterprise/governance#compliance-api).

150 365

1511. Go to [Codex](https://chatgpt.com/codex) in the left-hand panel of ChatGPT.366## Step 7: Confirm and verify setup

1522. Select **Connect to GitHub** in the prompt composer if you’re not already connected.

153 - Sign in to GitHub.

1543. You can now use shared environments with your workspace or create your own environment.

1554. Try a task in both Ask and Code mode. For example:

156 - Ask: Find bugs in this codebase.

157 - Write code: Improve test coverage following the existing test patterns.

158 367

159## Track Codex usage368### What to verify

160 369

161- For workspaces with rate limits, use [Settings → Usage](https://chatgpt.com/codex/settings/usage) to view workspace metrics for Codex.370- Users can sign in to Codex local (ChatGPT or API key)

162- For more detail on enterprise governance, refer to the [Governance](https://developers.openai.com/codex/enterprise/governance) page.371- (If enabled) Users can sign in to Codex cloud (ChatGPT sign-in required)

163- For enterprise workspaces with flexible pricing, you can see credit usage in the ChatGPT workspace billing console.372- MFA and SSO requirements match your enterprise security policy

373- RBAC and workspace toggles produce the expected access behavior

374- Managed configuration applies for users

375- Governance data is visible for admins

164 376

165## Zero data retention (ZDR)377For authentication options and enterprise login restrictions, see [Authentication](https://developers.openai.com/codex/auth).

166 378

167Codex supports OpenAI organizations with [Zero Data Retention (ZDR)](https://platform.openai.com/docs/guides/your-data#zero-data-retention) enabled.379Once your team is confident with setup, you can roll Codex out to more teams and organizations.

enterprise/admin-setup.md Codex Docs, 2026-02-21 00:33 UTC → 2026-03-13 00:34 UTC