Assigning AEM Product Profiles assign-profiles-aem

In this part of the onboarding journey, you learn how to grant you team access to AEM using AEM product profiles.

Objective objective

After you have read the previous document in this onboarding journey, Create Environments, and have your cloud resources configured, grant your team access to AEM itself using AEM product profiles. As the system administrator, you do this by assigning AEM product profiles.

After reading this document, you should understand:

  • What AEM product profiles are.
  • How to add team members to AEM User product profile.
  • How to add team members to AEM Administrators product profile.

AEM Product Profiles aem-product-profiles

To use AEM, your team members must be assigned to at least one AEM product profile. Permissions to access Cloud Manager will not suffice. Users must belong to one of two product profiles:

  • AEM Users - This group includes normal users who perform everyday content authoring tasks.
  • AEM Administrators - This group includes users who are responsible for advanced features or AEM.
Every user assigned to an AEM as a Cloud Service product profile has read-only access to Cloud Manager via the Cloud Manager User role.
Users with the Cloud Manager User role only can log into Cloud Manager and navigate to the AEM author environments (if they exist) by using the Programs menu options. The Cloud Manager User role is not sufficient to access program details. If such access is needed, users must be granted additional roles by their system administrator.
See the Additional Resources section below for more information about Cloud Manager user roles.
Do not edit or delete the Product Profiles named AEM Administrators or AEM Users. Editing these profile names can break login to the AEM cloud instance.

Prerequisites prerequisites

Before you start reading this section, you should have the following information available about your team who will use AEM.

  • Names
  • Email addresses
  • Roles and responsibilities
For the purpose of onboarding, Adobe recommends that you initially add users who will participate in the immediate tasks, such as administrators, developers and content authors. You can continue the rest of the onboarding without adding all users. After you have finished onboarding, you can scale to a larger number of users later.

View AEM Product Profiles view-profiles

Follow these steps to see the AEM product profiles from the Admin Console.

  1. Log in to Admin Console at

  2. From the Overview page, select Adobe Experience Manager as a Cloud Service from the Products and services card.

    Products and services card

  3. Navigate and select the instance.

    Select instance

  4. You can see the list of AEM as a Cloud Service product profiles that can be assigned to a user based on their roles.

    Product profiles

Add Team Members to Product Profiles add-team-members

Now that you are familiar with the available profiles, you can assign them as necessary to your team members.

These tasks require you to be a system administrator with the Business Owner Cloud Manager product profile.

  1. Navigate to your program from Cloud Manager and select the Manage Access button from the context of the environment of interest.

    Mange access

  2. A new tab navigates you to the Admin Console from where you have access to the author instance of the environment. Select AEM Administrators or AEM Users based on the permissions this individual must be given.

    Assign access

  3. Select AEM Administrator or AEM User and click Add User as shown below and submit the necessary details to complete adding the team member.

    Add team member

  4. Repeat these steps for all environments including development, staging and production, if you have the information of team members who need access available.

The user you added will now have access to the AEM as a Cloud Service Author services!

End of the Journey? the-end

Congratulations! The users that you assigned to AEM as a Cloud Service product profiles are now ready to access the AEM authoring environment and start creating content with AEM as a Cloud Service. Likewise, developers can now access Cloud Manager to use git to store custom application code and deploy it. In this sense, your onboarding journey is complete and your users can now use AEMaaCS.

However if you would like to better understand how authors and developers use the system, you can continue on with two optional parts of this onboarding journey:

  • Developer and Deployment Manager Tasks - Where you learn how developers access git to store their custom code and deploy it using Cloud Manager pipelines.
  • AEM User Tasks - Where you learn how to access the AEM environment where you can start creating content.

Additional Resources additional-resources

The following are additional, optional resources if you would like to go beyond the content of the onboarding journey.