Custom permissions custom-permissions
Learn how you can use custom permissions to create new custom permission profiles with configurable permissions to restrict access to programs, pipelines and environments for Cloud Managers users.
Introduction introduction
Cloud Manager has a set of pre-defined roles that govern access to various Cloud Manager features:
- Business Owner
- Program Manager
- Deployment Manager
- Developer
Custom permissions allow users to create new custom permission profiles with configurable permissions to restrict access for Cloud Managers users to programs, pipelines and environments.
Use custom permissions using
Creating and using your own custom permissions requires the following three steps:
This section details these steps. You may find it useful to see the Terms and Configurable Permissions sections as you create your own custom permissions.
Create a new product profile create
First create a new product profile to which you can assign custom permissions.
-
Log into Cloud Manager at my.cloudmanager.adobe.com
-
Select the product AEM Managed Services.
-
Search for and instance with name matching the pattern
*-cloud-managerand click to manage users and permissions. -
You are redirected to the Products tab of the Admin Console, where you can manage users and permissions for Cloud Manager. In the Admin Console, click New Profile.
-
Provide the general details about the profile.
- Product profile name - A descriptive name for the profile
- Display name - An abbreviated name that is shown in the user interface (options)
- Description - An informative description of the profile explaining its purpose (optional)
- Notify users by email - When selected, the system notifies users by email when they are added to or removed from this profile.
-
Click Save.
The new product profile is saved and is visible in the list of product profiles in the Admin Console.
Assign custom permissions to the new product profile assign-permissions
Now that you have a new product profile, you can assign custom permissions to it.
-
In the Admin Console, click the name of the new product profile you just created.
-
In the window that opens, select the Permissions tab to view a list of editable permissions.
-
Click the Edit link for permission to edit it.
-
The Edit Permissions window opens.
- The permission you selected in the previous step is selected in the left column.
- The permission items available for assignment for the permission are in the middle column labeled Available Permission Items.
- The assigned permission items are in the right column labeled Included Permission Items.
-
Click the plus (
+) icon next to the permission item to add it to the column Included Permission Items. If necessary, click theiicon next to a permission item to learn more about it. -
At the top of the Available Permissions column, click Add all to add all permissions. Likewise, click Remove all to remove all the previously selected permissions.
-
When you are finished defining the permission items for your new product profile, click Save.
Your new product profile is now saved with its custom permissions.
Assign users to the new product profile assign-users
You can now assign users to the new product profile you created with custom permissions.
-
In the Admin Console, click the name of the new product profile to which you just assigned custom permissions.
-
In the window that opens, select the Users tab.
-
Click Add Users and assign users to your new product profile with custom permissions.
See Add users and user groups to a product profile of the document Manage product profiles for enterprise users for more details on how to use the Admin Console.
Configurable permissions configurable-permissions
The following permissions are available for creating custom profiles.
Organization-level permissions organization-level
Organization-level permissions are always applied across all programs within an organization.
One example of an organization-level permission in Cloud Manager is Repository Info Access. This permission lets users generate a username, password, and repository URL for accessing and contributing to customer projects. While the username and password remain consistent across all repositories in the organization, each program has a unique repository URL.
See the Source Code Repository for more information.
Terms terms
The following terms are used in creating and managing custom permissions and pre-defined roles.
Permission items refer to the scope where permissions are applied. Typically, it is one of the following.
Limitations limitations
Keep in mind the following limitations when using custom permissions:
- A limited set of permissions is available for creating custom profiles.
- Resources like program, environment, pipeline etc. created in Cloud Manager may take up two minutes to display in Admin Console for permission configuration.
- In rare scenarios where a custom permissions service fails to respond, predefined profiles are still available and users in predefined profiles still have appropriate access.
Frequently asked questions faq
Which permission profiles are predefined permission profiles?
- Business Owner
- Program Manager
- Deployment Manager
- Developer
For details on pre-defined roles, see Role-Based Permissions.
What happens to predefined permission profiles with introduction to custom profiles?
Default product profiles and Cloud Manager roles continue to work the same as before.
Can I edit predefined permission profiles?
No, default profiles are non-editable. You cannot add or remove permissions to the default permission profile. You can only add or remove users from predefined profiles.
Should I delete predefined permission profiles since custom profiles are now available?
Predefined permission profiles must not be deleted from the Admin Console.
Can I add users to multiple permission profiles?
Yes, A user can be part of multiple profiles including predefined and custom permission profiles. When a user is assigned to multiple profiles, the combined permissions from all the assigned permission profiles are available to that user.
What happens if a user has permission to edit an environment/pipeline but doesn’t have access to a program that contains the environment/pipeline?
In this scenario, the user is unable to access the environment or pipeline if they do not have the Program Access permissions containing the environment or pipeline.
What happens if I have both AEM as a Cloud Service and AMS programs in the same IMS org? Can I manage permissions from one profile? ams-and-aemaacs
Create a separate profile for each product type. That is, one for AEM as Cloud Service and one for Adobe Managed Services or AMS.