Limit which users in an organization can see a specific page?

[lhendricks]

Is there a way to set up Experience Builder so that different pages have different viewer access? For context, my team within my organization has sensitive information that we don't want other members of the organization to view without direct supervision and interpretation by my team. We want them to see a generalized version of the data so they know when they need to approach us for more information. 

I've searched extensively and haven't been able to find anything about whether or not this is possible. I believe that Hub has this capability, but we are going to be transitioning to Portal soon and are waiting to do any major development until we know how that will impact our workflows. 

[Hels77]

I'd like to know this too. Considering copying the app to create a different version which would contain addition pages, but if there's a way to do it within the one app that would be excellent.

[lhendricks]

Exactly! That's my current strategy (having two very similar apps for the different groups) but it would be nice to have it all in one. (Especially for the people on my team, so we can easily know which is which without having to rely on the naming convention or the metadata.)

[TonghuiMing · Accepted solution]

Currently, no finer level than an Experience Builder app (the pages inside one app cannot be saved as separated AGOL items) can be shared with different user types.

@lhendricks Your strategy mentioned above it the current way to go.