Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1564

Provisioning a user should respect domain claim settings

XMLWordPrintable

    • 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.

      Problem Definition

      When a new user is provisioned and your domain claim settings are set to "manually claim", the new user is still managed if their email contains the claimed domain.

      Suggested Solution

      The new user should be provisioned and unclaimed.

      Why this is important

      This would allow teams to easily claim a domain, manage just the right set of users but still harness provisioning. For example, to avoid unnecessary charges on their Access bill, a team may choose to unclaim users on their domain but still want to provision those users to automate group assignment (and thus product access).

      Workaround

      Their is currently no work around and this ticket will be updated when one becomes available.

            Unassigned Unassigned
            tbrothers Tyler B [Atlassian]
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: