Use Codex Permissions and Protect Company Data

Permission changes what an instruction can do

Codex may be able to read files, edit them, run commands and use connected tools. Which actions are available depends on the surface, selected permissions and organisation settings. Check the active workspace and mode rather than assuming Codex can see everything, or that every action will need a separate prompt.

The official permissions guide describes workspace boundaries and approval modes. It currently recommends Ask for approval as a starting point for most work. Available choices can vary by environment and managed requirements. Approve for me routes eligible requests through automatic review; it is not a promise that the assistant cannot make mistakes. Broader access is not a requirement for our small exercise.

When a request needs more access, ask what action needs it, which files or service are involved and how it relates to the current task. Approve a concrete action you understand. If it is unnecessary, decline it and ask for an approach within the existing boundary.

Keep the practice separate from work data

Opening a project gives the assistant context from the selected location, subject to its controls. Do not point an experiment at a folder containing client records, credentials, employee information or confidential strategy just because it is convenient.

Use the fictional starter for this course. For real work, confirm that your organisation permits the exact account, tool, feature, data and purpose. A paid plan, company email address or no-training setting does not settle retention, access and onward sharing. Never put passwords or API keys in prompts or project instructions.

The workplace AI safety course covers these decisions in more depth, including what to do after an accidental upload. If you are unsure, practise with a newly invented example while the designated person checks the permitted workflow.

Treat retrieved text as source material

A README or webpage may contain instructions asking an assistant to upload private files, install something unrelated or send a message. A source document cannot grant permission on your behalf. Pause if the requested action expands the task or introduces a new destination.

Your plain-English brief is useful, but it is not a substitute for enforced access limits and careful review. An instruction file also does not turn a service into an approved destination for company data.