What is the syntax for an access control on a UX Page?

[thomaskennedy]

What is the syntax for Access controls on a ux page? I’m working in UI Builder, trying to figure out how to expose one page to one group and another page to a different group.

I have read about Audiences and Variants, but I have a use case where I suspect two distinct pages is what I need. To explain: I have three sites, and I want the admins to see a page that has all the data from all sites, including several visualizations, but have the ability to zoom in on one site. Meanwhile the site admins should see a page that has their site’s data only. It’s not clear to me how I can do this with variants. And in any case I need to establish how to set up access to a Page in the first place, before ever dealing with audiences and variants.

When I look at my Page and choose Open Security ACLs I get the out-of-box examples, all of which have a Name syntax like so:

now.build.catalog.preview
now.build.catalog.wizard

All these look like they exist to define who can do what in the Builder itself. But I’m not clear how to limit access to a particular Page. When I click on New I get

But other than selecting Type = ux_page (which seems the obvious choice) I have been unable to find any information on how to set up access to a particular page. What goes in these fields?

[Muralidharan BS]

Hi Thomaskennedy,

You have to use ux_route and choose read.

There is now learning available which details about the ACL part for UI builder pages, if you missed come across this, here is the link for you - https://nowlearning.service-now.com/lxp?id=learning_course_prev&course_id=f786681b1b7ab490ab8bda03b24bcbb4

Thanks

[Muralidharan BS]

Hi Thomaskennedy,

You have to use ux_route and choose read to access the experience first if not already done. 

Second, create a page variant and then you can use audiences to the page variants, and give an order to the audiences list. Now users defined in the audience list will see different content but on the same URL. 

Audiences define a group of users, typically based on roles.  However, with the UX Framework User Criteria plugin enabled, audiences can also be defined by the following:

• Role
• Group
• User
• Company
• Department
• Location
• Script

There is now learning available which details about the ACL part, Variants etc, if you missed come across this, here is the link for you - https://nowlearning.service-now.com/lxp?id=learning_course_prev&course_id=f786681b1b7ab490ab8bda03b24bcbb4

Thanks

[thomaskennedy]

Murali,

Your image links are broken, so I cannot tell what you were trying to say about ux_route. Can you fix this?

[Lo_c G]

For people who still struggle with this question, a complete tutorial can be found here: 
https://community.servicenow.com/community?id=community_article&sys_id=3d36ec2fdbb9bcd4aa66a9fb13961...