While both roles have administrative capabilities, their scope of control is fundamentally different.
Admins operate at the workspace level.
Subscription Admins operate at the subscription level, across all workspaces.
Admin (Workspace-Level Control)
An Admin manages settings and resources within a specific workspace.
Admins can:
Manage and publish Agents within their workspace
Connect tools and integrations
Configure workspace-level settings
However, Admins cannot:
Edit user roles
Apply updates across the entire subscription
Enable or activate subscription-wide features (such as Scores or model access)
Enforce governance changes across multiple workspaces
Admins are limited to managing the workspace they are assigned to.
Subscription Admin (Subscription-Level Control)
A Subscription Admin has centralised control across the entire subscription — including all associated workspaces.
This means they can centrally orchestrate and apply updates across the entire subscription, including:
Enabling beta features subscription-wide
Activating Scores across all workspaces
Enabling or restricting AI models across the subscription
Updating user roles across all workspaces
Managing naming conventions across the subscription
Configuring and managing custom properties at scale
Managing integrations across all workspaces
Publishing Agents to one or multiple workspaces
Choosing whether tool connections are carried over when publishing
Subscription Admins are responsible for maintaining consistency, governance, and security across the full environment — not just within a single workspace.
Why This Distinction Matters
The key difference is scope of authority.
Admins manage individual workspaces.
Subscription Admins manage the entire subscription ecosystem.
If your organisation requires centralised governance, subscription-wide feature control, or user role management at scale, those capabilities require a Subscription Admin.