UI Builder workspace - how to setup user permission to avoid "403: You do not have permissions to access this page."

fran_oisschneid
ServiceNow Employee
ServiceNow Employee

Hello,

I created a new application in Studio.

I created in this application a new workspace experience using UI Builder.

It works well as an admin user.

End users can work well in the application back office, but they can't access the workspace, they get the error "403: You do not have permissions to access this page.".

I searched in docs, google, community, etc. but I didn't find any information to setup user permission to access a "New Experience" workspace.

Using ACL? Audience? Landing page configuration?

Any guidance is welcomed.

Please help!

Best regards.

1 ACCEPTED SOLUTION

fran_oisschneid
ServiceNow Employee
ServiceNow Employee

Hello,

 

I finally found the answer.

I need to create 2 ACLs:

  • One "ux_page" read ACL, with the name = workspace URL having slashes replaced by dots
  • One "ux_route" read ACL, with the name = workspace URL having slashes replaced by dots, plus ".*" 

Plus the user roles who can access.

 

If the workspace URL is "x/company_id/workspace_url":

  • The ux_page name is set with name = x.company_id.workspace_url
  • The ux_route name is set with name = x.company_id.workspace_url.*

 

Best regards.

View solution in original post

3 REPLIES 3

fran_oisschneid
ServiceNow Employee
ServiceNow Employee

Hello,

 

I finally found the answer.

I need to create 2 ACLs:

  • One "ux_page" read ACL, with the name = workspace URL having slashes replaced by dots
  • One "ux_route" read ACL, with the name = workspace URL having slashes replaced by dots, plus ".*" 

Plus the user roles who can access.

 

If the workspace URL is "x/company_id/workspace_url":

  • The ux_page name is set with name = x.company_id.workspace_url
  • The ux_route name is set with name = x.company_id.workspace_url.*

 

Best regards.

Hello François,

We have almost the same issue. We created the ACLs you mentioned in READ operation. 

We can access our pages now, thanks to you. But unfortunately, our components inside the pages don't load (we are only using ServiceNow component, no custom ones). Do you have any intel ? 

Kind regards.

Lo_c G
Giga Contributor

All good, I found a complete tutorial here:
https://community.servicenow.com/community?id=community_article&sys_id=3d36ec2fdbb9bcd4aa66a9fb13961951