Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-1176

Provide a way for users removed from the provisioning scope to remain active

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Problem:

      When a SCIM synced user is removed from a provisioned group in IdP, the user immediately gets deactivated. This happens when the user's Atlassian cloud app assignment in the IdP is intact due to its membership in a single group. So the removal of user from this IdP group breaks the Atlassian application assignment for the user and the corresponding Atlassian account is de-activated.

      Suggestion:

      There are cases when the users have access to multiple cloud instances some via the IdP group product access and others via accepting invitation from the site admin. The accounts need to remain active even if they have been removed from the Idp groups. So in such cases, requesting for an alternative to prevent the user's getting de-activated when their group membership is removed.

      ie. Provide a way for admins to remove delete the SCIM data (synced status) of an account via the UI.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              07b65cdcf5f4 npv (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: