You do not have access to this resource error on AEM Cloud Service Integrations tab despite correct Developer Access + Product Profile assignments | Community
Skip to main content
V
Vignesh6369
Level 1
August 5, 2026
Question

You do not have access to this resource error on AEM Cloud Service Integrations tab despite correct Developer Access + Product Profile assignments

  • August 5, 2026
  • 1 reply
  • 52 views

When navigating to Tools > Integrations in the AEM author console (https://author-p552-e2209.adobeaemcloud.com), I consistently get:

An error has occurred.
You do not have access to this resource.
Sorry for the inconvenience.

The "Local token" section below the error still renders fine (Get local token / Create new technical account buttons are visible and clickable), but the main Technical Accounts panel above it fails to load with this error.

What I've already verified/tried:

  1. Confirmed in Adobe Admin Console that i has Developer Access assigned specifically to the correct product: "Adobe Experience Manager as a Cloud Service - " — not just the generic org-level AEMaaCS product.
  2. Assigned the "AEM Administrators - author - Program 212 - Environment 209" product profile to this user (previously only had Integrations/Developer profiles on the generic org-level product).
  3. Saved the change in Admin Console, confirmed it shows up under the user's assigned products.
  4. Fully signed out and back in, and also tried a hard refresh — no change.
  5. The Developer Console (https://developer-...) also throws a 403 when trying to list Technical Accounts for this same environment, even though the page itself loads and correctly shows the environment/pod details.

Question:

  • Is there an additional Cloud Manager–level role (e.g., "Deployment Manager" or "System Administrator" on the Cloud Manager program itself, separate from the AEM product profile in Admin Console) required to view/manage Technical Accounts and Integrations?
  • Does the entitlement typically take longer than ~20-30 minutes to propagate after a profile change, and if so, is there a way to check propagation status?
  • Are there known cases where the "Integrations - Cloud Service" and "AEM Administrators - author" profiles don't fully cover Technical Account visibility, and a separate/explicit "Cloud Manager User" role is required?

Any guidance on the correct permission combination for viewing/creating Technical Accounts under Tools > Integrations would be appreciated.

1 reply

Shashi_Mulugu
Community Advisor and User Group Leader
Shashi_MuluguCommunity Advisor and User Group Leader
Community Advisor and User Group Leader
August 11, 2026

Hi ​@Vignesh6369 ,

This issue happens because Technical Accounts / Service Credentials in AEM as a Cloud Service are managed via the Developer Console API / IMS integration layer, which relies on Cloud Manager role permissions rather than just AEM Author Product Profiles.

Root Causes & Fixes

1. Missing Cloud Manager "Developer" or "Deployment Manager" Role

 * The Cause: AEM Administrators - author gives admin rights inside the AEM repository itself, but viewing/managing Technical Accounts calls the underlying Cloud Manager / Developer Console services.

 * Fix: In Adobe Admin Console, go to Products > Cloud Manager for your organization/program and ensure the user is assigned the Developer or Deployment Manager product profile/role under Cloud Manager.

2. Developer Access Assigned at Org Level instead of Program/Env Level

 * The Cause: If "Developer Access" is assigned generically at the Org level or to a different Program/Environment context, Developer Console API calls to author-p552-e2209 will fail with a 403 (which matches the Developer Console 403 error observed).

 * Fix: Ensure Developer Access is granted specifically under Adobe Experience Manager as a Cloud Service > Program 212.

3. IMS Token / Entitlement Cache Propagation Delay

 * The Cause: IMS profile updates can take up to 1–2 hours to propagate across Developer Manager APIs, even if local AEM login succeeds earlier.

 * Fix: Have the user re-authenticate via an Incognito session or clear the IMS cookie (adobeid_...) to force token renewal after role assignment.

Key Takeaway

To view and manage Technical Accounts under Tools > Integrations (and avoid the 403 on Developer Console), the user needs both:

 * AEM Product Profile: AEM Administrators - author (for repository access).

 * Cloud Manager Role: Developer role assigned specifically on the Cloud Manager product in Admin Console (for IMS Technical Account management API access).

 

Terms & ConditionsAccessibility statement

Loading footer...