Issue Summary

If site access for an Atlassian account was revoked manually via the Has access on site toggle, if that account is synced via SCIM user provisioning and activated/reactivated, the Has access on site toggle has to be switched back on manually for the account to regain site/product access.

Steps to Reproduce

This was reproduced using Okta as the identity provider but has not yet been tested with other integrations.

1. Revoke site access manually for an Atlassian account via the Has access on site toggle in Products -> User Management -> Users.
2. Deactivate or unassign the user from the Atlassian Cloud application at the identity provider.
   • This results in the Atlassian account being deactivated as expected.
3. Reactivate or reassign the user in the Atlassian Cloud application at the identity provider.
   • This reactivates the Atlassian account and adds them to the assigned groups that grant product access as expected.
   • However, the Has access on site toggle remains off and the account cannot actually access products on that site until an administrator grants them site access manually.

Expected Results

An Atlassian account that is synced via SCIM and activated should not only be reactivated, but should also be granted site access if it had been revoked manually so that an administrator does not have to grant them access manually.

Actual Results

The Atlassian account is reactivated and added to the groups that grant product access. However, the Has access on site toggle remains off and the account cannot actually access products on that site until an administrator grants them site access manually.

Workaround

For any accounts with this issue an administrator for that site needs to toggle Has access on site on manually in Products -> User Management -> Users.