"Secret" Projects

[jarretjo]

Hi, I have a requirement to keep some Projects as secret so that they may only be viewed by certain Users. I guess Im not the first to have this requirement so I was wondering about other peoples experience and how they went about it.

Perhaps theres even a standard way of doing this.

Kind Regards

[Laszlo Balla]

I do not know if there is a specific way to do this out of the box, but in general I would think about the following:

• custom scope with custom roles - do not necessarily need to create any custom tables, but you could add custom columns to existing tables within this scope (e.g. a flag to indicate secret projects).
• ACLs and before query business rule on the relevant tables that use your custom role to show/hide records.

This may not be the most elegant solution, but certainly simple, and you can keep all this customization in a separate scope at least.

[Kiran58]

Check new feature Data filtration which enables us to control the data visibility.

https://docs.servicenow.com/en-US/bundle/tokyo-platform-security/page/administer/security/concept/da...

[jarretjo]

Thanks Kiran58 and Laszlo Ballo. 

I just checked out the new Data Filtration feature and that seems to be the way ahead! I will update this post to let you know how it works!

[jarretjo]

I kinda like this Data Filtration. Its straight forward to restrict users not see some Projects /Demands though they can still see all other Projects /Demands.  I just using Subject Group (Assignment Group) atm.

My next Use Case would be for Users to see only Projects /Demands for which they are a member of the Assignment Group. 

Any ideas?