DA Permissions App

[usman-khalid]

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):

Fix #

Test URLs:

• Before: https://main--da-blog-tools--aemsites.aem.live
• After: https://--da-blog-tools--aemsites.aem.live

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run all PSI checks
• Re-run failed PSI checks
• Re-sync branch

Commits

• d25cd12 ✅ (latest)
• f86aec8 ✅
• c489bde ✅

[amol-anand]

1. In tools/apps/da-permissions/da-permissions.js:217-220, every non-write permission is treated as read. DA also supports an empty action for deny/none, so this can misrepresent locked-down content in the UI and removing that entry could accidentally widen access.

2. In tools/apps/da-permissions/api.js:9-16 and tools/apps/da-permissions/da-permissions.js:289-302, any successful config fetch is treated as editable admin access. We should show that the user is in read-only mode and cannot make adjustments if they only have read access.

[usman-khalid]

1. In tools/apps/da-permissions/da-permissions.js:217-220, every non-write permission is treated as read. DA also supports an empty action for deny/none, so this can misrepresent locked-down content in the UI and removing that entry could accidentally widen access.
2. In tools/apps/da-permissions/api.js:9-16 and tools/apps/da-permissions/da-permissions.js:289-302, any successful config fetch is treated as editable admin access. We should show that the user is in read-only mode and cannot make adjustments if they only have read access.

Both fixed.