Verify Domain - Old users vs New Group users in Guard

Controls product access? 

Do you know where I can find that? We dont have anything sync'd to Azure or AD. 

By "product access group," I mean the group granting Jira/Confluence licenses under admin.atlassian.com → Directory → Groups.

So when you aren't syncing Azure AD, your cloud groups are the sole source of truth. Testing an Atlassian Guard policy on a new 3-user group will only affect those 3 people. The remaining 97 users will be completely safe, as long as you leave their original access group intact and apply the new policy only to the test group.

Thanks Arkadiusz.

One more question. I'm guessing that "Identity Providers" isn't the same thing as verifying your Domain? 

If we apply the same logic I was asking before does this still work? So under Admin -> Security -> Security Guide -> Identity Providers

it seems to be. 

Tim

@Tim Kennett 

You're right. Domain verification proves ownership for account management, but doesn't automatically remove users or strip product access. Access is controlled by your internal Atlassian groups. SSO and provisioning only work if you connect an IdP like Azure AD or Okta.

When testing Atlassian Guard, start with a small, separate policy for test users. Avoid linking the whole domain to an IdP until you understand the impact.

Best,

Arkadiusz 🤠