Jenna Palacio
ServiceNow Employee

Hello.  I rolled out a version of ServiceNow knowledge where we had restricted 'views'/access. We moved from a knowledge application where users had different access based on where they were located (it was a global company) and if they were HR or IT. This was done to keep people from accessing information they shouldn't (IT from seeing sensitive HR documents, people in the US from seeing EMEA procedures, etc.). It took a bit of configuration, but what was eventually decided was that access would be based on roles. You would have a location role (NA, Germany, France, Canada, etc.), a work role (HR, IT), and possibly another work role (internal, external, customer). 

Since we had knowledge teams around the globe, we only had a few templates (for IT, HR, and self-service), and anything in workflow rolled up to the appropriate KM team based on the geographic role (EMEA IT KM team, NA IT KM team, APAC HR KM Team...). Honestly, the most effort was in figuring out who would be assigned what roles and creating the spreadsheets to upload so everyone was assigned to them. It worked great. 

View solution in original post