Custom Permissions custom-permissions
Learn how you can use custom permissions to create 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 which govern access to various Cloud Manager features:
- Business Owner
- Program Manager
- Deployment Manager
- Developer
Custom permissions let users create custom permission profiles with configurable permissions to restrict access for Cloud Managers users to programs, pipelines, and environments.
Using Custom Permissions using
To create and use your own custom permissions, it requires 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 product profile before to which you can assign custom permissions.
-
Log into Cloud Manager at .
-
On the Cloud Manager landing page, select the Manage Access button.
- 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, select the New Profile button.
-
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 UI (options)
- Description - An informative description of the profile explaining its purpose (optional)
- Notify users by email - Users receive an email notification when they are added to or removed from this profile.
-
Select Save when complete.
The new product profile is saved and is visible in the list of product profiles in the Admin Console.
Assign Custom Permissions to Profile assign-permissions
Now that you have a new product profile, you can assign custom permissions to it.
-
In the Admin Console, select the name of the new product profile you created.
-
In the window that opens, select the Permissions tab to view a list of editable permissions.
-
Select the Edit link of a permission so you can edit it.
-
The Edit Permission 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.
-
Select the plus (
+) icon next to the permission item so you can add it to the column Included Permission Items.- Select the
iicon next to a permission item if you want to learn more about it.
- Select the
-
Select the Add all button at the top of the Available Permissions column so you can add all permissions.
-
Select Save when you are finished defining the permission items for your new product profile.
Your new product profile is now saved with its custom permissions.
Assign Users to the Custom Permissions assign-users
You can now assign users to the new product profile you created with custom permissions.
-
In the Admin Console, select the name of the new product profile to which you assigned custom permissions.
-
In the window that opens, select the Users tab.
-
Select the Add Users button and assign users to your new product profile with custom permissions.
See the section Add users and user groups to a product profile of the document 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 refer to permissions which are always given across all programs in an organization.
The following permissions are organization-level permissions:
-
Program Create - This permission lets users create a program in the organization.
-
Repository Info Access This tenant/organization level permission allows users to generate a username, password, and repository URL for access and contributing to a customer project.
- The username and password for repository access is common across all the repositories in the organization. However, the repository URL is unique to each program.
- See Accessing Repositories 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 permission is applied. Typically, it is one of the following.
Usage notes usage-notes
- A custom permissions profile also lists AMS programs, environments, and pipelines while configuring permissions.
- Resources like program, environment, and pipeline that were 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 AEM as a Cloud Service Team and Product Profiles.
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?
Do not delete predefined permission profiles 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 which contains the environment/pipeline?
In this case, the user is unable to access the environment or pipeline if they do not have the Program Access permissions containing the environment or pipeline.