{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieiul6pzq2xgwz6t2knjt27hfu7npt7mel4lq2qs3ymzjucg7vc5i",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3movakruneiu2"
  },
  "path": "/t/chatgpt-business-organization-wide-instructions-for-every-chat-and-codex-session/1384033#post_2",
  "publishedAt": "2026-06-22T15:15:54.000Z",
  "site": "https://community.openai.com",
  "textContent": "The strongest version of this is probably not one giant hidden system prompt. It should be an auditable instruction stack with scoped precedence.\n\nI would separate four layers: non-negotiable organization safety constraints, product-specific defaults, repo/project instructions, and user preferences. The important part is not just applying the policy, but showing the effective stack when something behaves differently than expected.\n\nFor Codex specifically, an “effective instructions” view would help a lot: org policy version, AGENTS.md sources, skill instructions, MCP/tool policy, and user-level preferences. That makes conflicts debuggable and makes security teams more comfortable with rollout.",
  "title": "ChatGPT Business: organization-wide instructions for every chat and Codex session"
}