visibility for portal and backend

[PamuruR]

Hi Everyone,

we have a requirement that, we have a group "Is employee"

if user is part of only isEmployee group then backend tables should not be accessible.

If user part of multiple groups and allowed to view the backend then user should be able to view the backend 

[KrishnaMohan]

Hi @PamuruR 

Refer below or The ServiceNow KB article KB0869746 provides a technical guide on how to implement role-based portal redirection. This allows you to automatically send different users to different portals (e.g., CSM vs. Service Portal) or the native UI (Back end) based on their assigned roles.

Note: above article is to implement role based portal redirection, you can make this based on groups or additional or own logics.

Here are some useful links and references
https://www.servicenow.com/docs/r/xanadu/platform-user-interface/service-portal/c_SPSSOLoginAndRedir...
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0869746
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0747432

If this helped to answer your query, please mark it helpful & accept the solution.
Thanks!
Krishnamohan

[Ankur Bawiskar]

@PamuruR 

do you mean this?

-> if user is member of this group then take that user to native

-> if user not member of this group then take that user where?

[lauri457]

I recommend utilizing the com.glide.explicit_roles plugin which will install the internal/external roles. I recall the ux_routes and ui_page acls require snc_internal to pass meaning ext users are not able to view the app shell or any ui page with the shell or without it. 

Either way it is less brittle to manage access via roles and not groups. You then give the role to the group