Cloud manager Environment visibility and permission restriction | Community
Skip to main content
M
MohammedSh6
Level 1
February 9, 2026
Solved

Cloud manager Environment visibility and permission restriction

  • February 9, 2026
  • 5 replies
  • 35 views

I have given access to user for  developer, deployment manager roles  in cloud manager for dev env from admin console.  However this user is seeing the other envrionments when logged in to cloud manger, he can hibernante/dehibernate these envs.  However there is no access to other env when he clicks other env. However He still sees these env links and option to add env button.  Is there any way to restrict env access links and option to hide Add env button on top. 

Best answer by AmitVishwakarma

Hi ​@MohammedSh6 ,

You cannot hide other environments or the “Add environment” button within the same program if the user must keep the Deployment Manager role.
Cloud Manager permissions are:

  • Program‑level, not environment‑level => a Deployment Manager for a program always sees all that program’s environments.
  • UI visibility (env tiles, Add env) is driven by roles from Admin Console product profiles (and org/product admin roles), not per‑environment scopes.

Thanks,
Amit

5 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
February 9, 2026

​@MohammedSh6 this is happening because you gave deployment manager role assigned, only give developer role who can just view.

 

But we cant restrict viewing of environments list in cloud manager but restrict from performing any actions(hibernate/de-hibernate)

M
MohammedSh6Author
Level 1
February 10, 2026

​@MohammedSh6 this is happening because you gave deployment manager role assigned, only give developer role who can just view.

 

But we cant restrict viewing of environments list in cloud manager but restrict from performing any actions(hibernate/de-hibernate)

That works but we need deployment manager role as user will be deploying the code. I cannot remove this role

Vishal_Anand
Vishal_Anand
Level 5
February 9, 2026

​@MohammedSh6  Root cause: Cloud Manager shows environment links when a user’s Adobe Admin Console product profile or org role grants broad visibility (product admin, org admin, or a profile scoped to multiple envs). The “Add environment” button appears for product/org admins only.

 

Quick fix:

  1. Go to Adobe Admin Console → Products → Cloud Manager → Product Profiles.
  2. Confirm the user’s product profile — ensure it’s scoped to the Dev environment only (or create a Dev‑only profile and assign it).
  3. Remove any org or product admin roles (e.g., Cloud Manager Administrator, Organization Administrator) from the user or any groups they belong to.
  4. Verify group/SSO mappings so the user isn’t indirectly granted wider access.
  5. Log out and back in (or clear cache); allow a few minutes for changes to propagate.

If links or the Add button still appear: open an Adobe Cloud Manager support ticket with org ID, user AdobeID, product profile screenshots and explain you want UI visibility limited to Dev - Adobe support can confirm tenant behavior or apply fixes for managed accounts.

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 12, 2026

This is most likely a role configuration issue in Admin Console.
 

Cloud Manager permissions are entirely controlled by the roles assigned in Adobe Admin Console under the Cloud Manager Product Profiles. If the user can see all environments, hibernate them, or see the Add Environment button, then they have been assigned a role that allows program-level access.
 

You should carefully review the role matrix here:

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/requirements/role-based-permissions 
 

Check the permissions matrix on that page and compare it with the role assigned to the user. Roles like Deployment Manager, Program Manager, and Business Owner have broader control across all environments in a program.
 

If someone has been adjusting Product Profiles in Admin Console, they may have accidentally assigned the user to a profile with elevated permissions. Review the user’s group membership in Admin Console and verify which Cloud Manager role is actually being applied.
 

Environment visibility cannot be restricted per environment within the same program. It is determined strictly by the role assigned at the program level.

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    February 17, 2026

    ​@MohammedSh6 I wanted to follow up and see if your issue has been resolved. If you were able to find a solution—either from the responses above or on your own—we’d appreciate it if you could share the details for the benefit of others. Additionally, if any reply was helpful, marking it as accepted helps future members quickly identify effective solutions. Thank you for helping improve the community experience.

    Kautuk Sahni
    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity AdvisorAccepted solution
    Community Advisor
    February 18, 2026

    Hi ​@MohammedSh6 ,

    You cannot hide other environments or the “Add environment” button within the same program if the user must keep the Deployment Manager role.
    Cloud Manager permissions are:

    • Program‑level, not environment‑level => a Deployment Manager for a program always sees all that program’s environments.
    • UI visibility (env tiles, Add env) is driven by roles from Admin Console product profiles (and org/product admin roles), not per‑environment scopes.

    Thanks,
    Amit

      Terms & ConditionsAccessibility statement

      Loading footer...