Answer: To rotate a Codex access token, create a replacement token, update the secret in the runner, scheduler, or secret manager, run a smoke test with the new token, then revoke the old token from the Access tokens page. Workspace owners and admins can revoke any workspace token, while members with access token permission can revoke only the tokens they created. Status: Confirmed Entry: tool/codex/permissions-and-security/rotate-or-revoke-token Revision: 1 Digest: sha256:2d725be5c78a319b (changes whenever the content changes) Timeline: Created: 2026-11-13T03:49:02Z Last changed: 2026-11-13T03:49:02Z Last verified: 2026-11-20T13:36:56Z Next check: 2026-11-21T13:36:56Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Step 1 | Create a replacement token. | [1] | 2026-11-20 Step 2 | Update the secret in the runner, scheduler, or secret manager. | [1] | 2026-11-20 Step 3 | Run a smoke test with the new token. | [1] | 2026-11-20 Step 4 | Revoke the old token from [Access tokens](https://chatgpt.com/admin/access-tokens). | [1] | 2026-11-20 Who can revoke any workspace token | workspace owners and admins | [1] | 2026-11-20 Who can revoke only their own tokens | Members with access token permission | [1] | 2026-11-20 Sources: [1] OpenAI. "Access tokens". https://learn.chatgpt.com/docs/enterprise/access-tokens.md Role: primary. Accessed: 2026-11-20T13:36:56Z Quote: "1. Create a replacement token." (Supports: Step 1) Quote: "2. Update the secret in the runner, scheduler, or secret manager." (Supports: Step 2) Quote: "3. Run a smoke test with the new token." (Supports: Step 3) Quote: "4. Revoke the old token from [Access tokens](https://chatgpt.com/admin/access-tokens)." (Supports: Step 4) Quote: "workspace owners and admins can revoke any workspace token" (Supports: Who can revoke any workspace token) Quote: "Members with access token permission can revoke only the tokens they created." (Supports: Who can revoke only their own tokens) Snapshot SHA-256: bd5b1821bc59ec534504caa8ed5960cd649425527f67680ba39a9aa389cec95a (captured 2026-11-13T03:49:00Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:49:02Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:36:56Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:36:56Z Last attempt: 2026-11-20T13:36:56Z Notes and limitations: Extracted automatically from a single official source (section "Rotate or revoke a token"). Related: https://latestn.com/tool/codex/permissions-and-security/rule-fields What fields can I set in a Codex rule, such as pattern and decision? https://latestn.com/tool/codex/permissions-and-security/run-bulk-security-scans How do I run bulk security scans across multiple repositories with Codex Security? https://latestn.com/tool/codex/permissions-and-security/run-first-local-scan How do I run my first local security scan with the Codex Security plugin? https://latestn.com/tool/codex/permissions-and-security/restrict-network-destinations How do I restrict network destinations for Codex Cloud and local Codex? https://latestn.com/tool/codex/permissions-and-security/review-findings-across-scans How do I review findings across scans in the Codex Security workbench? https://latestn.com/tool/codex/permissions-and-security/review-sensitive-actions How do I review sensitive Codex actions before they run? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:49:02Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/rotate-or-revoke-token/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/permissions-and-security/rotate-or-revoke-token POST: https://latestn.com/dispute/tool/codex/permissions-and-security/rotate-or-revoke-token with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/rotate-or-revoke-token?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I rotate or revoke a Codex access token? Revision 1, last verified 2026-11-20T13:36:56Z. https://latestn.com/tool/codex/permissions-and-security/rotate-or-revoke-token (accessed 2026-11-21T10:06:29Z). @misc{LatestN_tool_codex_permissions_and_security_rotate_or_revoke_token_r1, title = {How do I rotate or revoke a Codex access token?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/rotate-or-revoke-token}}, note = {Revision 1; digest sha256:2d725be5c78a319b; last verified 2026-11-20T13:36:56Z; accessed 2026-11-21T10:06:29Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/permissions-and-security/rotate-or-revoke-token