UI Builder access control

Fernnn
Tera Contributor

I'm new to UIB and looking for advice on how to handle access.

Is it good practice to use the same page for different roles/audiences?

How should I retrieve access information? Custom data source? Something else?


I know form components handle access per ACLs cleanly, but there are a lot of scenarios that aren't covered.

2 REPLIES 2

Tanushree Maiti
Tera Patron

Hi @Fernnn 

 

Handling access in UI Builder (UIB) is best managed using Audiences and Role etc .

Add an audience to your UI Builder page 

UI Builder - Component Visibility Logic

Manage UI Builder pages and page variants 

https://www.youtube.com/watch?v=n5D6_2fdnP8

https://www.youtube.com/watch?v=MM24xvPPTD8

https://www.youtube.com/watch?v=73xu_j7QtOU&t=3s

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti
In ServiceNow UI Builder, you can create page variants based on the audience to display different versions of a page for different users or roles. This is useful when you need to tailor the UI experience based on user roles, groups, or specific conditions. Steps to Create a Page Variant Based on ...
Official product documentation: https://docs.servicenow.com/bundle/rome-application-development/page/administer/ui-builder/concept/ui-builder-overview.html#d1732985e102
In this video, we explore Role-Based Experiences and Security in ServiceNow UI Builder You'll Learn: What role-based experiences mean in UI Builder How to configure Experience Roles inside Service Operations Workspace How Experience Settings control workspace access How ACLs (Access Control Lists)

I understand that convention. I'm asking about the technical "how". Should I make a data resource to query for whether a user can do an action? Is there an OOTB ACL evaluator? Is there some other design convention that I'm overlooking?