Use PDIs? Take our 5-minute survey to help shape the PDI roadmap.

User Criteria Not Restricting Catalog Visibility in Employee Center

Hrithikah
Tera Expert

Hi Community,

I am trying to restrict catalog visibility in Employee Center so that only users from specific HR and Service Desk groups can view it.

I tested both:

  • Standard User Criteria (Groups)
  • Scripted User Criteria

The User Criteria is added to Available For on the Catalog and Category, but it is not working as expected. Some users outside the allowed groups can still see the catalog, while some users within the allowed groups cannot.

Has anyone experienced similar behavior in Employee Center? Are there any additional configurations or known limitations that could affect User Criteria enforcement?

Thanks in advance.

6 REPLIES 6

Anand__99
Mega Sage

Hi @Hrithikah ,

 

Use the User Criteria Diagnostic tool to view how your user criteria is working.

https://www.servicenow.com/docs/r/servicenow-platform/service-catalog/debug-user-criteria-cat-item.h...

 

Also, user criteria applied to catalog category does not work on Employee Center it works on Classic Service Portal.

 

Thanks

Anand

Ankur Bawiskar
Tera Patron

@Hrithikah 

screenshots of the config please

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

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

MalakaSilva
Giga Contributor

Apply User Criteria directly to Catalog Items.
Do not rely solely on Category-level User Criteria
Make sure to check that Not Available For User Criteria is not there for a subset of users.

Tanushree Maiti
Tera Patron

Hi @Hrithikah 

 

  • Navigate to Content Taxonomy/Topics, ensure user criteria is explicitly enabled and applied to the specific  Taxonomy Topics corresponding to your HR and Service Desk sections

Refer: Enable user criteria for topics 

New: User Criteria for Taxonomy Topics in Employee Center

 

  • Clear your browser cache, log out and back in, or test via impersonation by affected user
  • Review all attached criteria on the item. Use Not Available For to explicitly block general fallback groups. There should not be any conflict between Available For and Not available for.
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