Problem

When a user attempts to access an Atlassian product and is blocked due to Just-in-Time (JIT) provisioning not being configured or not applying to their account, they are presented with a generic error or access-denied page that provides little to no actionable guidance.

For individual users — particularly in large enterprise environments — this creates a frustrating dead end. The user does not know:

Why they were blocked

Whether they need to contact their IT/identity team

What information to provide when raising a support request

Whether this is something they can resolve themselves or needs to be escalated to Atlassian via their IT admin

This results in unnecessary support ticket volume, delayed resolution, and a poor first-time experience for end users.

Proposed Solution

Improve the JIT provisioning blocked-access page to be more informative and actionable. Specifically:

Explain why access was blocked — e.g., "Your organisation uses managed authentication. Your account was not automatically provisioned."

Provide tiered self-service guidance based on the likely user context:

Related

https://jira.atlassian.com/browse/AX-1392 — Improve Request Access feature (allow custom message on access request page)