Blocking Employee Center for certain users

[Ryan S]

How can I prevent certain users (based on their roles) from accessing the employee center?

I can redirect to /sp or the SOW easily enough, but that doesn't prevent the user from simply changing the url to /esc. I want to prevent them from accessing /esc unless they have a certain role.

[Ankur Bawiskar · Accepted solution]

@Ryan S 

let them go to ESC portal, you can add a widget on that homepage or use UI script and check what role they have

if they don't satisfy then take them to SOW or SP or wherever you want

1) Approach 1: Widget

How to strictly restrict Portal access by Role? 

2) Approach 2: UI Script

Another method is to use UI script, see below link for approach

Solution: Redirecting Users to the CSM Portal Based on Roles in ServiceNow

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ryan S]

The first link talks about using the SP User Criteria Plugin, but after installing that (and clearing cache) I don't see options to add user criteria to my portal page view (sp_portal). What am I missing? Using user criteria seems like the easiest option.

As for the second option, that is redirecting users based on a role but I want something slightly different. I think I see how the approach might be leveraged, but probably just too tired to see it now. Actually, the user should be able to get to /esc if they have role or are in a certain 'company'. If they don't, they shouldn't have access to /esc and would only ever get to /sp given the redirect is in place.

[Ankur Bawiskar]

@Ryan S 

you can go with the 1st approach.

that 1st approach doesn't require User Criteria Plugin

In that a widget is added to Portal Header which checks the role etc and redirects.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ryan S]

Ok I think I got them backwards, but the custom widget route you're saying would work. Of course, that requires customization. There doesn't appear to be any OOTB way to solve this though. Is that true? What is the purpose of the SP  User Criteria Plugin then?