Select to view content in your preferred language

Page Visibility Restrictions

419
1
04-10-2026 02:09 PM
ScottHiggins_PVGIS
Occasional Contributor

Hi all,

I am wondering if anyone has had any success with the new page visibility functionality, particularly in Experience Builder Dev. We have an application use case we are hoping to use this functionality with, but in are preliminary testing it doesn't seem to be achieving what we though the functionality was introduced to do.

Our general use case is as follows, as a concept:

We have an application with 5 pages.

We were hoping that pages 1,3,5 could be shared with Utility Group #1 and Pages 2,4 shared with Utility Group #2. This means, or so we thought, that Utility Group #1 wouldnt even be aware that pages 2,4 are inside the application, and Utility Group #2 wouldnt be burdened to know that Pages 1,3,5 were there, as the visibility would limit them from seeing.

In our Experience Builder Developer 1.19, this seemed like it was in the realm of possibilities with this new functionality.

I.e. You may want parts of your app to be viewable by some users but not all. You can restrict access to specific app pages to accounts with certain user types or membership in certain groups. From the online documentation. To me that implies visibility, not additional prompts.

However, in our test, the Pages not shared with Utility Group 1 are still visible, and accessible, in these cases the 'Creating map failed' warning still appears as those two maps arent shared with Group 1, and all it does is prompt them to try another login credential or to ignore click to ignore. Visibility to these pages doesnt seem to be limited.

Of course, with Dev edition, we are in the localhost, so to test this, we open the published app in incognito mode with a User set to Utility Group 1 (or 2, only noting conceptually as to what we tested). 

And here, page visibility isn't limited at all, it is only additional prompts that is provided for ignore or another login, and the "Map creation failed" when this user tries to access that page from the menu.

Has anyone had any success with this functionality? Or is what this purports to do and what it actually does not the same thing? Any advice would be appreciated.

 

0 Kudos
1 Reply
SunshineLuke90
Occasional Contributor

I am in the same boat, having issues with developer edition, and am trying to use a combination of the login widget and the page visibility restrictions. When I turn on page visibility restrictions on some of my pages, they just disappear from the application entirely.

On the other hand, in ArcGIS Online, the page visibility restriction has been fantastic, doing exactly what it purports to do (limiting access to pages depending on group access), so I know it's possible for everything to work nicely, I think it's just something with the current developer edition that is causing page visibility to not function in the way that I expect.

I would appreciate anyone who has more experience, or someone from Esri to chime in on where the issue might lie. I'm going to be taking a look over the next few weeks to see if I can find out where the issue is occurring and hopefully patch a fix in.