· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →OpenAI v0.1.28
Manage ChatGPT workspaces for workspace owners or admins.
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Who are the highest-usage users this month?
Developer declarations; not independently tested. Listing last checked Nov 8, 2026.
From the marketplace listing
Built for ChatGPT workspace owners and admins to manage members, groups, roles, permissions, GPTs, and Skills, and review Agents and audit logs. Monitor usage and billing across Chat, Codex, and Work, and manage usage limits and alerts. Available only in ChatGPT Work and Codex modes. Includes alternative-authentication setup guidance with explicit access choices, private credential entry, and approved read verification.
Language: English · Automatically detected from descriptions.
Exact text from the indicated source. A mention alone does not establish support for your task.
Interactive Read Write
admin-console agents alternative-authentication analytics audit-logs billing codex gpts groups invitations members permissions provider-setup roles service-accounts shared-links skills spending usage-limits workspace-administration
Built for ChatGPT workspace owners and admins to manage members, groups, roles, permissions, GPTs, and Skills, and review Agents and audit logs. Monitor usage and billing across Chat, Codex, and Work, and manage usage limits and alerts. Guide alternative authentication and provider credential setup when available.
Built for ChatGPT workspace owners and admins to manage members, groups, roles, permissions, GPTs, and Skills, and review Agents and audit logs. Monitor usage and billing across Chat, Codex, and Work, and manage usage limits and alerts. Available only in ChatGPT Work and Codex modes. Includes alternative-authentication setup guidance with explicit access choices, private credential entry, and approved read verification.
· 1 observation
Package or technical metadata updated
View technical comparison →· 3 observations
Skill instructions changed from “and sharing migrated” to “choosing whether to carry over sharing, and bulk sharing of new or already-migrated”.
View comparison →Package or technical metadata updated
View technical comparison →· 3 observations
Skill instructions changed from “and sharing.” to “sharing, explicitly confirmed deletion, and explicitly requested attached-file metadata. File metadata is supplementary and never added to standard reports.”.
View comparison →Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 3 observations
Skill instructions: added “plugin inventory:** Read [export-workspace-plugins](workflows/export-workspace-plugins/WORKFLOW.md) for a downloadable CSV of plugins visible in the...”.
View comparison →Version changed from 0.1.20 to 0.1.21
View technical comparison →Find competitors to follow as you develop your plugin.
Manage VesselVault orders, leads, tickets, and part quotes through your authenticated account.
Shared terms: admin, authentication, permission
RNTOR connects ChatGPT to your flexible workspace management platform, giving authorized teams instant access to operational data for rep...
Shared terms: workspace, billing, guide, member
Connect an AI assistant to authorized Omniaseo workspace operations.
Shared terms: workspace, limit, usage, permission
Clinked helps users find and manage workspace groups, members, files, folders, notes, tasks, and events directly from ChatGPT.
Shared terms: workspace, group, member
Connect ChatGPT to Jaggle to search, review, organize, and safely update permission-filtered workspace work.
Shared terms: workspace, permission, review
--- name: admin-console description: Manage ChatGPT workspace members, groups, roles, usage limits, billing, Agents, GPTs, Skills, audit logs, workspace, Codex or Work analytics, private cohorts, and alternative authentication and provider service-account setup. --- # ChatGPT Admin ## Use ChatGPT Admin in Work or Codex Determine the current product surface and mode only from explicit system, developer, or trusted runtime context. If the plugin is running in positively identified standard ChatGPT Chat Mode, do not call a tool, inspect the workspace, or begin an administrative workflow. Respond only: "ChatGPT Admin is not supported in Chat. Please start a new conversation in ChatGPT Work or Codex and select ChatGPT Admin there." Continue normally in ChatGPT Work Mode, Codex, or when the current mode cannot be positively identified. Do not infer Chat Mode from a missing tool, shell access, workspace files, the administrator's request, or another unavailable capability. Chat and Work are separate conversations; never claim that the current conversation, attachments, or selected plugin transfer automatically. Use this single entrypoint for ChatGPT workspace administration and analytics. Identify the requested workflow, then read its linked instructions completely before calling a tool or taking action. Load only the instructions relevant to the current request and apply the shared identity-resolution, timestamp, change-preview, and retry rules below throughout that workflow. ## Resolve people and resources once Reuse exact identities already supplied by the administrator, returned earlier in the current conversation, or available from trusted memory that is explicitly associated with the same authenticated workspace. This applies to people, email addresses, authentication-user IDs, account-user IDs, groups, roles, Agents, GPTs, Skills, invitations, requests, and other canonical resource identifiers. An exact name-to-identity match already established for that workspace does not need another search. - If the requested tool accepts an already-known canonical ID or exact email address, use it directly. Do not list members or resources, fetch an object, or repeat a search just to rediscover or confirm the same identity. - Maintain distinct identifier families: authentication-user `id`, workspace-scoped `account_user_id`, email address, `group_id`, `role_id`, `agent_id`, `gpt_id`, `skill_id`, invitation ID, and request ID are not interchangeable. If only an email is known but the requested tool requires an authentication-user ID or account-user ID, resolve the missing identifier once; use an email directly when the tool accepts an email. - When several people or resources are requested, first collect every identity already available from the request, conversation, earlier tool results, and trusted same-workspace memory. Resolve only genuinely missing identities; reuse one appropriate bounded listing or supported search result across all matching requested targets instead of repeating the same listing once per person or resource. Preserve bounded pagination and ask for clarification if a name is ambiguous. - Reuse metadata already returned for the same resource rather than performing list-then-get calls. Fetch details only when the administrator actually requests information not already available, when the operation requires a missing security-sensitive fact such as whether a group is SCIM-managed or a role is built-in, or when the administrator explicitly requests a refresh. - Verify relationships between users, groups, roles, and other resources using tools that return the actual identities involved. Counts, summaries, and incomplete results do not establish whether a specific relationship exists. If the relationship cannot be verified, say so rather than inferring or inventing an answer. - A follow-up comparison inherits the previously established product, metric, resource population, reporting surface, date range, and filters
Preview of the first 4,000 characters. Read full instructions →
plugin_connector_1p_e4d796f7afc48191bf6af2220a55fdd6
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.