# Codex Permission Profiles: Beta Release **URL:** \ **Category:** Codex\ **Created:** [June 29, 2026, 5:10pm UTC](https://community.openai.com/t/codex-permission-profiles-beta-release/1385275 "2026-06-29T17:10:58Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![VeitB](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/veitb/32/712987_2.png) [@VeitB](https://community.openai.com/u/VeitB)\ **Post date:** [June 29, 2026, 5:10pm UTC](https://community.openai.com/t/codex-permission-profiles-beta-release/1385275/1 "2026-06-29T17:10:58Z")
Sharing this here because it’s a recurring topic in the developer community: OpenAI has introduced [reusable permission profiles](https://developers.openai.com/codex/permissions) that can be inherited across tasks. These profiles replace the older coarse sandbox modes with more specific OS-enforced rules for file access, including read, write, and deny rules for paths such as \*\*/\*.env. The same profile can also define network access by domain and control Unix socket access. Admins can set fail-closed allowlists, which means access is blocked unless it is explicitly allowed. The practical benefit is clearer least-privilege control per task instead of broad sandbox settings. Since this is an early release there are a few things to consider. Make sure to read the disclaimer in the docs.