Learn More About User Management in Atlassian Cloud
(+ Tips to Reduce Licensing Cost!)

1. Atlassian Cloud Licensing(Assign License)
In Atlassian Cloud, users are granted access to Atlassian products based on the following conditions:
Condition | Description |
User added to Access Group | When a user is added to Access Group linked to product licenses such as Jira or Confluence, the user will automatically granted with access. |
Authorized Admin | Users assigned with organization admin, site admin, or product admin permissions automatically granted with access. |
2. Atlassian Cloud Licensing(Remove License)
In Atlassian Cloud, license access will be removed based on the followings:
Condition | Description |
Remove user from Access Group | When removing a user from the Access Group linked to product license such as Jira/Confluence, access will be revoked(license revoked). |
Suspend User | User's access will be suspended if the organization administrator suspends the user(license revoked). |
Remove User | User's access will be revoked if the organization administrator removes the user from the organization directory. |
3. User Management via AD integration (SCIM-based Provisioning)
Atlassian Cloud integrated with External Identity Provider(IDPs) like Azure AD and Okta to provide user and group synchronization based on the Standard for Cross-domain Identity Management(SCIM)
- Automatic Synchronization Features:
- User created in AD will automatically be registered in Atlassian Cloud.
- Users deactivated in AD will automatically be suspended in Atlassian Cloud(license reclaim)
- Group Synchronization and Manage License
- The group structure in AD is automatically replicated to Atlassian Cloud, allowing you to use AD groups directly when configuring Access groups in Atlassian.
- ๐ฌIn other words, you can manage Jira and Confluence licenses via group directly from AD.
Common Use Cases
Item | Description |
Add User | When a user is added to AD, the change is automatically reflected in Atlassian Cloud. |
Deactivate User | When an employee resigns and is deactivated in AD, the corresponding Atlassian user is automatically suspended. |
Management of licenses based on user groups | Only users included in the AD group named 'jira-users' are allowed to access to Jira Cloud. If a user no longer needs access, removing them from the 'jira-users' group in AD is automatically reflected in Atlassian Cloud. |
4. AD integration + manage license directly within Atlassian Cloud
By integrating the IDP (e.g., Azure AD, Okta) with Atlassian Cloud via SCIM, users and groups are automatically synchronized, while license assignment (Access Group allocation) is managed manually within Atlassian Cloud.
Operating Model:
1. User Provisioning Automation
- Users provisioning are automatically created in Atlassian Cloud through SCIM integration with AD(or IDP).
- At this stage, users are only added to the directory and are not granted access.
2. Limited Use of Group Synchronization
- Groups from the IDP are synchronized to Atlassian; however, Access Groups (e.g., jira-users, confluence-users) are created and managed manually within Atlassian Cloud.
- This allows selective license assignment by adding only eligible users to the appropriate Access Groups.
3. Automatic User Deactivation
- When a user is deactivated in AD, the corresponding user in Atlassian Cloud is automatically suspended, ensuring they no longer have access to the app.
4. User Access (License Assignment) Managed by Atlassian Admins
- Whether a user will actually use Jira or Confluence is determined by the accountable team in Atlassian Cloud. They manually assign access by adding users to the appropriate Access Groups.
๐ฌThis model is especially suitable for organizations where IDP administrators and Atlassian administrators are two separate roles.
Common Use Cases
Item | Description |
New Employee Onboarding | When added to AD, the user is automatically created in the Atlassian directory. |
Access Granted(License Assignment) | Add the user to internal Atlassian groups (e.g., jira-users, confluence-users). |
Access Revoke(License Removal) | Remove the user from internal Atlassian groups (jira-users, confluence-users). |
Employee Offboarding | When the account is deactivated in AD, the user is automatically suspended in Atlassian. |
5. Direct User Management in Atlassian Cloud
- User invitations, removals, and group settings must be performed manually. (Registration and deletion via CSV are possible.)
- Identification of unused users/licenses and updates require separate monitoring and manual management by administrators.
6. User and License Management Using the Flexible User License Plugin
Flexible User License is a plugin designed to efficiently manage users and licenses in Atlassian Cloud, both automatically or manually.
Automatic User Management Features:
- All users
- Specific groups
- Specific domains
- External users (based on domain)
- Last activity date (e.g., users inactive for 30 days)
- Total license count (e.g., remove users if license seats exceed 100)
- Removal from Access Groups automatically upon events triggered
- User suspension
- Schedule for recurrence workflow (e.g., daily, every Monday)
Manual User Management Features:
- Rule-based manual execution
- instantly run rules set for automatic management
- Direct user search and bulk operations
- Search all users, specific groups, inactive users, etc.
- Select users for the following actions:
- Remove from Access Groups
- Suspend user
- Remove user
Common Use Cases
Scenario | Application Method |
Remove users inactive in Jira for 30 days | (Automation)Rule-based setting runs daily to remove users inactive for 30 days from Access Groups. |
Manage external users inactive for 7 days (specific domains) | (Automation)Rule-based setting runs daily to suspend external users from specified domains after 7 days of inactivity period. |
Quarterly user cleanup | Manual execution to perform bulk removals at a time |
๐Visit Flexible Studio Atlassian Marketplace for a free trial
๐Visit Flexible Studio Official Website for more info about the plugin
Learn More About User Management in Atlassian Cloud
(+ Tips to Reduce Licensing Cost!)
1. Atlassian Cloud Licensing(Assign License)
In Atlassian Cloud, users are granted access to Atlassian products based on the following conditions:
2. Atlassian Cloud Licensing(Remove License)
In Atlassian Cloud, license access will be removed based on the followings:
3. User Management via AD integration (SCIM-based Provisioning)
Atlassian Cloud integrated with External Identity Provider(IDPs) like Azure AD and Okta to provide user and group synchronization based on the Standard for Cross-domain Identity Management(SCIM)
Common Use Cases
If a user no longer needs access, removing them from the 'jira-users' group in AD is automatically reflected in Atlassian Cloud.
4. AD integration + manage license directly within Atlassian Cloud
By integrating the IDP (e.g., Azure AD, Okta) with Atlassian Cloud via SCIM, users and groups are automatically synchronized, while license assignment (Access Group allocation) is managed manually within Atlassian Cloud.
Operating Model:
1. User Provisioning Automation
2. Limited Use of Group Synchronization
3. Automatic User Deactivation
4. User Access (License Assignment) Managed by Atlassian Admins
๐ฌThis model is especially suitable for organizations where IDP administrators and Atlassian administrators are two separate roles.
Common Use Cases
5. Direct User Management in Atlassian Cloud
6. User and License Management Using the Flexible User License Plugin
Flexible User License is a plugin designed to efficiently manage users and licenses in Atlassian Cloud, both automatically or manually.
Automatic User Management Features:
Manual User Management Features:
Common Use Cases
๐Visit Flexible Studio Atlassian Marketplace for a free trial
๐Visit Flexible Studio Official Website for more info about the plugin