ACP-520 Questions and Answers

When you click “Grant access to Jira Software” in the access request, the user is granted access to Jira Software only. They are not added to multiple product access groups, granted the User role for Jira Software, added to only one default group, or granted any Product Admin roles. References: Manage product access, [Manage users and groups]

A direct cause for the “engineers” group having a lot more members than you have added manually is that it is a default group for Jira Software product access. This means that any new user who joins your site and has access to Jira Software will automatically be added to the “engineers” group. You can check and change the default group for Jira Software by going to Products > Jira Software > Manage product > Product roles.

References = [Default groups and permissions] and [Manage role and product permissions]

Currently, you can only create one sandbox for each linked product1. Since you have only two products (Jira Software and Confluence), and you already have a sandbox for Confluence, you cannot create any more sandboxes for your organization.

References: Manage product sandboxes

The most likely root cause of Omar being able to see Jira projects is that he belongs to a group that has access to both Confluence and Jira products. Groups are used to manage users who need the same permissions or restrictions, and they can be assigned to multiple products. When you invite a user to join your site and a product, you can also add them to a group that has access to that product. However, if the group also has access to other products, the user will be able to see those products as well. To prevent this, you can either create a new group that only has access to Confluence, or remove the Jira access from the existing group that Omar is in.

References = [Manage groups] and [Give users access to products]

The status “Active” means that the user has an active account and can access the products they have been granted access to1. It does not imply anything about the user’s group membership, account type, last login time, or product access.

References:

• Manage users in your organization

This is because the access request shown in the image is for Confluence and the reason stated is “Needs to access Confluence”. Hence, Monica is granted the User role for Confluence, which allows her to view and edit pages and spaces in Confluence. She is not granted access to any other products or any Product Admin roles, which require higher permissions. She is also added to only one default group, which is the confluence-users group, unless the site admin has changed the default group for Confluence.

References = [Approve or deny product access requests], [Manage product access]

When Holly signed up for a new Confluence Cloud site, two groups were definitely created along with the site. These are the default groups for Confluence: confluence-users and site-admins. The confluence-users group grants access to Confluence and allows users to create and edit pages. The site-admins group grants administrative privileges for Confluence and allows users to manage global settings, templates, permissions, and more12

References = Manage product access, Manage groups

Atlassian Access is a subscription that connects your Atlassian cloud products to your identity provider. It allows you to enable enterprise-grade authentication features, and additional oversight, across your company domains1.

References: Understand Atlassian Access, Atlassian Access: Enhanced Cloud Data Security & Governance

Groups are used to manage users with your organization who need the same permissions or restrictions. You can assign groups to one or more products within your organization, such as Jira Software, Confluence, or Bitbucket1.

References: Manage groups, Create and update groups

The table is showing the total number of managed accounts in the organization and the number of deactivated accounts. The total number of managed accounts is the number ofbillable users in the organization, regardless of whether they have verified their email addresses or not. The deactivated accounts are the accounts that have been suspended by the organization admin and do not consume a license. Therefore, you can definitely conclude that you have 8 billable users in your organization12

References = View and manage your bill, Remove or suspend a user

Deleting the group “jira-software-users-acme” means that all the users in that group lose their product access to Jira Software1. This means that they can no longer perform any actions that require the Jira Software User role, such as updating an agile board2. The other options are not directly affected by deleting the group, as they depend on other factors such as personal settings, Confluence permissions, service project roles, and API tokens.

References:

• Manage product access
• Manage product roles

If Ann’s email domain is not verified by your organization, it means that you do not own or manage her account. However, she may have a managed account in another organization that has verified her domain. In that case, you cannot enforce security policies, deactivate, or delete her account12.

References:

• Verify a domain to manage accounts
• Solved: Verify domain - Missing accounts

By removing the default group from the Jira Software User product role, you can prevent new users from automatically getting access to Jira Software when they join your site. This way, you can control who gets access to Jira Software and how many licenses are consumed.

ReferencesManage product access Product roles and permissions

For Atlassian Access billing, users on paid plans, like the Confluence Enterprise plan, are included in the bill. Atlassian Access provides security and centralized administration across all Atlassian Cloud products. Users on free plans, deactivated accounts, and portal-only customers (who typically access only a service desk portal and do not use licensed seats) are not counted as billable users for Atlassian Access.