AEP - Adobe IO - Unable to Edit existing IO projects as they are Read-Only

Last update: Tue May 28 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Learn why some projects containing the Adobe Experience Platform API are locked in ‘Read-Only’ and about the issues with the permissions granted to the user in AEP.

Description description

Environment

Adobe Experience Platform (AEP)

Issue/Symptoms

When opening the Adobe IO console, you may find that some projects containing the Adobe Experience Platform API are locked in ‘Read-Only’.

Also, when looking at the Product Profiles associated with the API, it is likely you see ‘deprecated’ profiles.

Since the Adobe Experience platform (AEP) permissions have been migrated to the AEP UI itself, some of the old product profiles that were in the Admin Console have been deprecated. As such, this is creating a discrepancy with the permissions granted to the user in AEP.

Resolution resolution

To resolve this issue:

A system Admin will need to log in to the Adobe IO console, and edit the project API so that all ‘deprecated’ profiles are removed.
Once saved, the only profile that should be present is the one called ‘Default Production All Access’.
You can then log out and log back in as the user who was seeing the ‘Read-only’ lock. This should now have disappeared.

recommendation-more-help

3d58f420-19b5-47a0-a122-5c9dab55ec7f