Answer: You manage privileges and permissions for the Codex GitHub Action using inputs such as `safety-strategy` (default `drop-sudo`), `unprivileged-user`, `read-only`, `sandbox`, and `allow-users`/`allow-bots`. These control exposure, restrict who can trigger the workflow, and limit filesystem and network access. Status: Confirmed Entry: tool/codex/permissions-and-security/manage-privileges Revision: 1 Digest: sha256:ead29899f5c3f183 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:51:31Z Last changed: 2026-11-13T03:51:31Z Last verified: 2026-11-20T13:39:52Z Next check: 2026-11-21T13:39:52Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of safety-strategy default | drop-sudo | [1] | 2026-11-20 unprivileged-user pairing | unprivileged-user | [1] | 2026-11-20 read-only behavior | read-only | [1] | 2026-11-20 sandbox behavior | sandbox | [1] | 2026-11-20 trigger restriction inputs | allow-users | [1] | 2026-11-20 default trigger access | write access | [1] | 2026-11-20 Sources: [1] OpenAI. "Codex GitHub Action". https://learn.chatgpt.com/docs/github-action.md Role: primary. Accessed: 2026-11-20T13:39:52Z Quote: "`safety-strategy` (default `drop-sudo`) removes `sudo` before running Codex." (Supports: safety-strategy default) Quote: "`unprivileged-user` pairs `safety-strategy: unprivileged-user` with `codex-user` to run Codex as a specific account." (Supports: unprivileged-user pairing) Quote: "`read-only` keeps Codex from changing files or using the network, but it still runs with elevated privileges." (Supports: read-only behavior) Quote: "`sandbox` limits filesystem and network access within Codex itself." (Supports: sandbox behavior) Quote: "`allow-users` and `allow-bots` restrict who can trigger the workflow." (Supports: trigger restriction inputs) Quote: "By default only users with write access can run the action; list extra trusted accounts explicitly or leave the field empty for the default behavior." (Supports: default trigger access) Snapshot SHA-256: 3c3a244ef87fffb064114e388f4c7827b3ddc55b712f5aec50f2719a3cf1bc6a (captured 2026-11-13T03:51:29Z) 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:51:31Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:39:52Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:39:52Z Last attempt: 2026-11-20T13:39:52Z Notes and limitations: Extracted automatically from a single official source (section "Manage privileges"). Related: https://latestn.com/tool/codex/permissions-and-security/manual-security-review-of-changes How do I run a manual security review of code changes in Codex? https://latestn.com/tool/codex/permissions-and-security/migrate-sandbox-to-profiles How do I migrate Codex from older sandbox settings to permission profiles? https://latestn.com/tool/codex/permissions-and-security/migrate-untrusted-approval-policy How do I migrate from the retired untrusted approval policy in Codex? https://latestn.com/tool/codex/permissions-and-security/how-policies-combine How do Global, Local, and Codex Cloud policies combine in Codex Agent Security? https://latestn.com/tool/codex/permissions-and-security/inspect-repository-history How do I inspect repository history in the Codex Security workbench? https://latestn.com/tool/codex/permissions-and-security/isolate-environment-cybersecurity How do I isolate the environment when running Codex for cybersecurity work? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:51:31Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/manage-privileges/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/manage-privileges POST: https://latestn.com/dispute/tool/codex/permissions-and-security/manage-privileges with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/manage-privileges?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I manage privileges and permissions for the Codex GitHub Action? Revision 1, last verified 2026-11-20T13:39:52Z. https://latestn.com/tool/codex/permissions-and-security/manage-privileges (accessed 2026-11-21T10:03:45Z). @misc{LatestN_tool_codex_permissions_and_security_manage_privileges_r1, title = {How do I manage privileges and permissions for the Codex GitHub Action?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/manage-privileges}}, note = {Revision 1; digest sha256:ead29899f5c3f183; last verified 2026-11-20T13:39:52Z; accessed 2026-11-21T10:03:45Z} } 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/manage-privileges