Answer: Create a named profile under `[permissions.]`, then set the top-level `default_permissions` key to that profile name or to one of the built-ins (`:read-only`, `:workspace`, `:danger-full-access`). Status: Confirmed Entry: tool/codex/permissions-and-security/define-select-permission-profile Revision: 1 Digest: sha256:7ce175bbb2ed3727 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:52:14Z Last changed: 2026-11-13T03:52:14Z Last verified: 2026-11-20T13:40:41Z Next check: 2026-11-21T13:40:41Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of profile definition syntax | [permissions.] | [1] | 2026-11-20 selection key | default_permissions | [1] | 2026-11-20 built-in profile 1 | :read-only | [1] | 2026-11-20 built-in profile 2 | :workspace | [1] | 2026-11-20 built-in profile 3 | :danger-full-access | [1] | 2026-11-20 example profile name | project-edit | [1] | 2026-11-20 enterprise restriction key | allowed_permission_profiles | [1] | 2026-11-20 Sources: [1] OpenAI. "Permissions". https://learn.chatgpt.com/docs/permissions.md Role: primary. Accessed: 2026-11-20T13:40:41Z Quote: "Create a named profile under `[permissions.]`, then set the top-level" (Supports: profile definition syntax) Quote: "`default_permissions` key to that profile name or to one of the built-ins above." (Supports: selection key) Quote: "`:read-only` keeps local command execution read-only." (Supports: built-in profile 1) Quote: "`:workspace` allows writes inside the active workspace roots and system temp directories." (Supports: built-in profile 2) Quote: "`:danger-full-access` removes local sandbox restrictions and should be used" (Supports: built-in profile 3) Quote: "In this example, `project-edit` is a user-defined profile name, not a built-in" (Supports: example profile name) Quote: "`allowed_permission_profiles` is present, omitted profiles are denied," (Supports: enterprise restriction key) Snapshot SHA-256: 1af24fb0126aba2d5eb43f8a1094bcf9e465e21c94ffeae78ba7dad874466318 (captured 2026-11-13T03:52:14Z) 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:52:14Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:40:41Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:40:41Z Last attempt: 2026-11-20T13:40:41Z Notes and limitations: Extracted automatically from a single official source (section "Define and select a profile"). Related: https://latestn.com/tool/codex/permissions-and-security/deny-reads-paths-globs How do I deny reads to specific paths or globs in a Codex permission profile? https://latestn.com/tool/codex/permissions-and-security/domain-allowlist How do I restrict which domains Codex Cloud (Legacy) agents can access? https://latestn.com/tool/codex/permissions-and-security/edit-repository-threat-model How do I edit the threat model for a monitored repository in Codex? https://latestn.com/tool/codex/permissions-and-security/create-rules-file How do I create a rules file to control which commands Codex can run outside the sandbox? https://latestn.com/tool/codex/permissions-and-security/create-service-account-access-token How do I create an access token for a Codex service account? https://latestn.com/tool/codex/permissions-and-security/default-sandbox-approval-settings What are the default sandbox and approval settings for Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:52:14Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/define-select-permission-profile/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/define-select-permission-profile POST: https://latestn.com/dispute/tool/codex/permissions-and-security/define-select-permission-profile with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/define-select-permission-profile?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I define and select a permission profile in Codex? Revision 1, last verified 2026-11-20T13:40:41Z. https://latestn.com/tool/codex/permissions-and-security/define-select-permission-profile (accessed 2026-11-21T10:03:11Z). @misc{LatestN_tool_codex_permissions_and_security_define_select_permission_profile_r1, title = {How do I define and select a permission profile in Codex?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/define-select-permission-profile}}, note = {Revision 1; digest sha256:7ce175bbb2ed3727; last verified 2026-11-20T13:40:41Z; accessed 2026-11-21T10:03:11Z} } 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/define-select-permission-profile