We have enabled SAML in Atlassian Access for our organization. We want all of our customers to have single-sign-on access as customers in Jira Service Desk. We do not want them to be "portal only" customers since portal only customers are not provided SAML authentication.
Our identity provider (Azure) is not yet supported for User Provisioning in Atlassian Access, so the way I am provisioning accounts for our employees is by "Inviting" them (I'm adding them without sending the invitation) to our Jira cloud instance, but without access to either Jira or Confluence (so they are not licensed users). This process works great and the customers I have added this way can immediately sign into the Help Center using their Azure credentials. Once they access the Help Center for the first time they also show up as managed users in Atlassian Access. Until they use our Help Center, they are not listed as managed users in Atlassian Access, but they do appear as users in our Jira cloud environment as users who have never logged in.
Our expectation is that these accounts could sit there until they decide they want to login for the first time... which could be weeks or months from now. I'm concerned that these accounts might expire if they are not logged into within 7 days or so. However when I filter our list of users I do not see them listed as "pending invitation." They only appear when I filter for active users. It just says they have never logged in.
Can anyone confirm that users added in this way will not expire or disappear?
Thank you,
Sean
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.