ATLASSIAN ACP-520 - Atlassian Cloud Organization Admin Certification

The only outcome that is not possible for Edmund is that he is granted org admin privileges. This is because org admin privileges are not related to product access or product roles, but to organization settings and management. To grant Edmund org admin privileges, you would need to go to Settings > Organization admins and add him there. The other outcomes are possible depending on the product access settings and the groups that Edmund belongs to.

References = [Give users access to products] and [Manage organization admins]

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

The Product admin role for Jira Administration is only available for groups that have access to Jira Software1. The “confluence-admins” group does not have access to Jira Software by default, so you cannot grant them this role. You can only grant this role to groups that have the Jira Software User role or the Jira Software Admin role2.

References:

Manage groups

Manage product roles

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]

By unselecting the User product role for Confluence, you are removing the site-admins group from the default groups that manage roles for that product1. This means that ACME site admins will lose their Confluence admin permissions, such as managing Confluence settings, space permissions, etc2. They will still be able to see Confluence users, but not edit their roles or access.

References: Default groups and permissions, Confluence Admin Permission Levels Explained

Martha needs to be able to use and update global templates and blueprints. The correct product access configuration for Martha is Confluence Administration with Product admin role. This role allows her to manage global templates and blueprints, as well as other site-wide settings for Confluence. She also needs the User role for Confluence to access and edit pages.

References = Manage product access, Administer global templates

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

When you add a domain to user access settings, you can specify the default product role for each product in your organization. This determines the level of access that users with verified email addresses from that domain will have when they join your site. If you set the product role to None, users will not have access to that product unless you manually grant them access later.

ReferencesSpecify how users get site access User access settings

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