"Grant access" button on Product Access tab is misleading when user already has product access

[Milan Kostic]

Category: Admin Console / User Management UX

Description:

In the redesigned Atlassian Administration console, when I navigate to a user's profile → Product Access tab, a prominent blue "Grant access" button is always displayed — even when the user already has product access (e.g., Jira Software).

Why this is a problem:

In the previous admin UI, this page used toggle sliders per product. If a slider was enabled, it was immediately clear the user had access. Seeing a "Grant access" action meant the user had no access at all. Admins have relied on this mental model for years.

The new UI breaks this expectation:

1. No clear "current access" summary — There's no prominent indicator (e.g., "✓ Currently has access to: Jira Software") displayed before or alongside the button to reassure the admin.

2. Button label is ambiguous — "Grant access" reads as "this user has no access yet" rather than "add access to additional products."

3. Risk of over-provisioning — An admin unfamiliar with the new design may click the button thinking the user needs access, then inadvertently add products the user shouldn't have.

Suggested improvements:

• Rename the button to "Grant additional access" or "Add product access" to signal that the user may already have some products.

• Display a visible summary of current product access (e.g., a list or badges) above or near the button so admins can see at a glance what the user already has without scrolling.

• Consider a contextual label: "This user has access to 1 product. Grant access to more?"

Environment:

• Atlassian Cloud admin console (admin.atlassian.com)

• Org admin / Jira admin role

• Observed on: May 2026

Impact: Medium — causes confusion and delays for organization admins performing routine user management tasks, and increases risk of accidental product over-provisioning.

[Dirk Ronsmans]

Hi @Milan Kostic ,

You might want to raise this as an issue on the support portal (https://support.atlassian.com/contact)

This way it will most likely get made in to a bug report/suggestion on the public tracker.

[Scott Allen]

Agree with this. They should fix this. 

[Tim Martin]

I don't mind the new interface - as someone who admins many orgs, some of which have many sites and apps. I'm guessing you're still on the original user management experience?

The problem with any sort of summary/toggle/badge/indicator is Atlassian are moving away from site-based user directories with only single instances of apps. Also, roles are no longer simply just "user" or not. So just saying someone has "Confluence access" is no longer valid - are they a guest, user access admin, user? And which instance(s)?

This gets complicated when you have SCIM provisioned groups mapped into app roles. If you care about governance, it's not just about having a role, but about how that role is provided (ie, which groups). So, I do agree that the experience around the "Grant access" button could be improved. But perhaps more so around a final confirmation showing exactly what changes I'm making to someone's access (current -> new) including group membership.