Select to view content in your preferred language

Accessing Experience Builder with administrative privileges

357
6
07-19-2024 11:47 AM
Labels (1)
BrandonCranfield
Occasional Contributor

Hi everyone! We are running an on-prem, multi-machine Enterprise deployment sitting at version 11.3. One issue we are seeing is administrative users, such as myself, are not able to access ExB applications created by other users within the organization in order to assist in configuration/troubleshooting. The error received is "Sorry, you do not have permissions to access this application."

 

This was not an issue with 11.1 as an administrator could edit anything within the Enterprise. Would be nice to know we are not the only ones running into this issue!!

6 Replies
Ke_Xu
by Esri Contributor
Esri Contributor

Hi BrandonCranfield,

Was ExB applications created by other users shared within the organization?

 

Thanks,

Ke

0 Kudos
BrandonCranfield
Occasional Contributor

Hi Ke_Xu,

All ExB applications tested were created by users of the organization. All had a variety of sharing methods applied including the following: owner, owner + group shared, organization, org + group, public, public + group. Even ExB applications created by other administrators and shared to the organization and public were not able to be accessed by other administrators. All applications adhered to a strict "creator-owned editing policy." This last statement added for clear picture purposes. Nothing stated explicitly this was in effect.

0 Kudos
Laura
by MVP Regular Contributor
MVP Regular Contributor

I can access others in 11.2

0 Kudos
BrandonCranfield
Occasional Contributor

This is only an issue in version 11.3 as far as we are tracking.

0 Kudos
NMHolman_ACS
New Contributor

Any updates on this? We're seeing it as well after upgrading to 11.3

0 Kudos
BrandonCranfield
Occasional Contributor

Hello all, I've been doing additional testing and I believe this particular issue is intentional. If the Experience in question is shared in a group that has the "Shared Update" capability and administrators are added to that group, they are able to edit as well. I believe the concept behind this is additional security for applications created by users are protected from being edited by individuals with elevated permissions. The security model makes sense but does require a few more steps taken to have the ability to edit. Any thoughts from the community?

0 Kudos