-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
1
Problem Statement
The Platform Usage page in Atlassian Administration (Insights → Platform Usage) is currently accessible only to Organization Administrators. With the rollout of Usage-Based Pricing (UBP) and usage visibility beginning September 1, 2026, product-specific administrators — particularly Bitbucket workspace admins — have a critical need to monitor consumption metrics (build minutes, Git LFS storage, automation steps) that directly impact their operations and billing.
Today, the only way to grant someone access to Platform Usage is to elevate them to Organization Administrator, which provides a much broader scope of access than what is needed simply to view usage data. This creates unnecessary bottlenecks and forces organizations to either:
- Over-provision org admin access just to allow usage monitoring, or
- Funnel all usage inquiries through a small number of org admins, creating a single point of failure
While Billing Administrators can view some usage data through the Billing panel (subscription details), they have no access to the Platform Usage page in the Admin Hub. This creates a fragmented experience where usage data exists in two different surfaces with different access requirements — and for partner-managed customers, even the Billing panel path is unavailable since the Billing Admin role is held by the partner, not the end customer.
The problem is further compounded for organizations with partner-managed subscriptions, where the end customer has no self-service path to Platform Usage data whatsoever unless explicitly granted Org Admin access — a role that may be inappropriate or impractical to assign broadly.
Who Is Affected
- Bitbucket workspace administrators who manage build pipelines and LFS storage but cannot see how their workspace contributes to org-level usage
- Product administrators for any Atlassian product who need to monitor metered usage ahead of UBP enforcement
- Billing administrators, who can see usage data in the Billing panel but cannot access the Platform Usage page in the Admin Hub
- Organizations with partner-managed subscriptions, where the end customer has no direct path to Platform Usage data at all since the Billing Admin role is held by the partner
Expected Behavior
Product Admins and/or Workspace Admins should be able to view Platform Usage data — at minimum for the products they administer — without requiring full Organization Administrator privileges. Possible approaches could include:
- A read-only "Usage Viewer" role scoped to Insights → Platform Usage
- Extending Product Admin permissions to include read access to usage data for their specific product
- Extending Billing Admin access to include the Platform Usage page in the Admin Hub, aligning it with the usage data already available to them in the Billing panel
- A configurable permission that Org Admins can delegate to specific users or groups
Business Context
With UBP enforcement beginning December 3, 2026, organizations need their operational teams to have direct visibility into usage trends so they can proactively manage consumption and avoid unexpected overage charges. Restricting full metered usage visibility to Org Admins only — who are often not the people managing day-to-day product operations — creates a critical visibility gap at the exact moment when usage awareness matters most.
The current fragmentation between the Billing panel and the Platform Usage page in the Admin Hub adds unnecessary confusion: customers and admins expect billing-related roles to have billing-relevant visibility, and the current state does not meet that expectation.
Additional Context
This request originates from direct customer feedback. A customer with multiple Bitbucket workspaces and a partner-managed subscription reported that none of their workspace administrators, Product Admins, Billing Admins, or technical contacts could access Platform Usage in the Admin Hub — leaving a single Org Admin as the only person in the organization with full visibility into UBP-relevant consumption data.