Keep Codex client accounts easy to identify.

Use names that match the engagement

A client name or workspace name gives you a faster check than an email address. If one client has several environments, include the role or team in the label.

Keep the list short. Remove profiles after an engagement ends or the client revokes access. Old profiles create noise and can make the wrong account look current.

Confirm identity before opening code

Select the client account from the menu, verify the check mark, then open the repository or task. This order keeps the account decision ahead of the work.

Finish or stop work tied to another account before switching. A task that already started can keep dependencies from its original account context.

• Name the account for the client.
• Switch before opening the client task.
• Remove access when the engagement ends.

Honor client policy

A client-managed account can carry rules for retention, administrators, data, and approved repositories. Account switching does not change those rules.

Keep client work under the account the client supplied. Do not use a personal account to avoid a limit or policy. Ask the client administrator when access or plan status blocks the work.

Use usage status as a planning signal

Read the reported usage under the client profile before a long task. The value can help you plan timing, but OpenAI and the client plan control the available capacity.

Unknown usage does not mean the profile cannot switch. Re-authorize expired access and confirm the current limit in Codex when the menu cannot read a value.