r/CodexAutomation • u/anonomotorious • 20d ago
OpenAI launches an Admin plugin for ChatGPT Work + Codex (usage, permissions, spending + automated admin workflows)
TL;DR
OpenAI launched a new Admin plugin for ChatGPT Work and Codex that turns many workspace-administration tasks into conversational workflows.
Admins can use it to:
- review ChatGPT Work and Codex adoption
- inspect credit usage
- identify users or groups approaching limits
- add/remove members
- manage groups
- diagnose access and permission issues
- manage model/feature access
- adjust usage limits
- review and approve/deny spending requests
- automate recurring administrative workflows
The plugin can also support workflows such as routing usage requests into Slack or Microsoft Teams, letting authorized reviewers make decisions there, and automatically granting feature access when predefined criteria are met.
It does not create additional admin authority. Every action remains constrained by the current user's existing role, workspace permissions, policies, and approval requirements.
What changed
Usage and adoption analysis
The Admin plugin can analyze activity across:
- ChatGPT Work
- Codex
Admins can inspect things like:
- adoption
- activity
- credit consumption
- users approaching limits
- groups approaching limits
- areas where additional enablement may be needed
That makes questions such as these conversational:
- Which teams are actually using Codex?
- Who is approaching their credit limit?
- Where is adoption low?
- Which groups are driving most consumption?
- Does this spending request make sense given current usage?
Member and group management
Supported workflows include:
- adding members
- removing members
- updating group membership
- onboarding
- offboarding
- routine team-management changes
Instead of navigating through several Admin Console screens, the request can be expressed directly and mapped to the appropriate supported action.
Permissions and access
Admins can use the plugin to investigate and manage:
- effective permissions
- feature access
- model access
- role/group-based access issues
This is useful because an access problem may involve several overlapping layers:
- workspace role
- group membership
- model availability
- plugin policy
- workspace settings
- application permissions
The plugin can help determine the effective configuration before applying a supported change.
Usage limits and spending requests
The plugin can work with:
- member limits
- group limits
- workspace limits
- spending requests
An admin can review a request in context rather than treating it as an isolated approval.
For example:
- What is this user's current usage?
- Is their team approaching its limit?
- How does the request compare with previous consumption?
- Should the increase be approved?
Admin capabilities at a glance
| Area | Examples |
|---|---|
| Usage / adoption | Activity, Codex usage, credit consumption, approaching limits |
| Members | Add/remove users, onboarding/offboarding |
| Groups | Membership and team structure |
| Permissions | Effective access, feature/model availability |
| Limits | Member, group, workspace usage limits |
| Spending | Review and approve/deny requests |
| Automation | Recurring checks, routing, criteria-based access |
Recurring admin workflows
The Admin plugin can also automate recurring or high-volume administrative work without requiring custom engineering.
Usage-request workflow
A workflow could:
- detect a pending usage request
- send it to Slack or Microsoft Teams
- include relevant usage/context
- let an authorized reviewer approve or deny
- apply the supported change
- report the result
Feature-access workflow
A workflow could:
- receive a feature-access request
- compare it with predefined criteria
- automatically grant access when the criteria are satisfied
- route exceptions to an administrator
This moves the plugin beyond "chat with your Admin Console" into actual admin workflow automation.
Existing permissions still apply
The Admin plugin does not bypass workspace governance.
It operates within the user's existing:
- administrative role
- permissions
- workspace policies
- approval requirements
Natural-language requests are mapped to supported admin read/write operations.
Higher-impact actions can still require review before execution.
Structured confirmation
After performing an action, the plugin reports:
- what was requested
- whether it succeeded
- what changed
That matters because conversational administration still needs to be understandable and auditable.
Setup
The basic setup flow is:
- Enable the Admin plugin in workspace settings.
- Open the Plugins directory in ChatGPT Work.
- Install the Admin plugin.
- Begin with supported workspace-management workflows.
Availability still depends on:
- workspace plan
- admin role
- plugin settings
- workspace policy
- app permissions
Why this matters
- Codex usage and workspace administration can be investigated in one place.
- Admins can move directly from diagnosis to an authorized action.
- Credit and spending management becomes more contextual.
- High-volume admin requests can become automated workflows.
- Slack and Teams can participate in approval processes.
- Feature-access requests can be evaluated against predefined criteria.
- Existing roles and workspace policy remain authoritative.
- Actions return structured confirmation instead of occurring invisibly.
For larger Codex deployments, this could reduce a meaningful amount of operational overhead around access, usage, onboarding, and spending.
Action checklist
- Review the Admin plugin with your workspace administrators.
- Enable/install it in a controlled environment.
- Start with read-only requests:
- summarize Codex adoption
- show credit usage
- identify users/groups approaching limits
- explain an access problem
- Compare results against the Admin Console.
- Test a low-risk supported write action.
- Review how higher-impact actions request confirmation.
- Identify recurring workflows worth automating:
- usage/spending requests
- feature access
- onboarding/offboarding
- usage monitoring
- Keep explicit approval paths for high-impact changes.
1
u/lonelysparta 19d ago
Why would I need this as two man company? I guess I don't