If a user signs in successfully but sees a No Access screen rather than any application, it means their account has been authenticated but they have not yet been assigned any roles within the platform.

Authentication and access are handled separately. The identity provider confirms who the user is, but the platform controls which applications and instances they can access through role assignments. Until at least one role is assigned, the platform has no applications to direct the user to and displays the No Access screen instead.

This typically happens when a user account is created in the identity provider before an administrator has completed the role configuration in the platform.

​

An administrator should assign the appropriate roles to the user's account. See Configuring User roles for instructions.

Once roles are assigned, the user should close their browser completely and sign in again. A full browser restart is more reliable than simply refreshing the page, because the No Access screen can be cached in the active browser session. If the screen persists after reopening the browser, the user can also try clearing browser cookies for the platform's domain, or waiting for the session to expire naturally before signing in again.