The current implementation of SAML SSO in Atlassian Cloud assumes that at least one application is used by all users within an account. Unfortunately this is not the case for us, and probably other customers as well.

For example, our company uses both JIRA Cloud and Confluence Cloud. Some users only have access to JIRA Cloud and others only have access to Confluence Cloud.

But with the SAML configuration options currently on offer we're unable to direct these users to their relevant application directly.

As a result we are forced to choose an application specific home page (in our case JIRA dashboard) as the SSO landing page. So Confluence Cloud only users are inconvenienced by SSO'ing into JIRA cloud and then navigating to Confluence via the Apps Menu.

We're trying to get around the issue but Atlassian Cloud supports one identity provider(IdP) per account so we're unable to create multiple IdP integrations. Multiple IdP integrations would allow us to provide multiple SSO landing pages, one per app.

Solution options include:

• Creating an app agnostic landing page that all users can access which is not tied to an app per se.
• Allowing multiple IdP integrations per account.
• etc.. It's your product so i'll let product dev decide.

Can you please review the issue described above and provide your feedback.
If there is a workaround to this issue can you please provide relevant information.

Thanks