Accessing Experience Builder with administrative privileges

[BrandonCranfield]

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!!

[Ke_Xu]

Hi BrandonCranfield,

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

Thanks,

Ke

[BrandonCranfield]

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.

[Laura]

I can access others in 11.2

[BrandonCranfield]

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

[EndreStoksethGeodata]

It looks like a a bug in 11.3.
First bullet point of "What's New" in 11.3 about access.
"Access — Only the app owner, organization administrators, and members of shared update groups to which an app is shared can open an experience in the builder."

The bug is reported her: https://support.esri.com/en-us/bug/administrators-do-not-have-editing-permissions-for-arcg-bug-00016...

[NMHolman_ACS]

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

[BrandonCranfield]

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?