Access Restrictions to other applications

Vivek13
Tera Contributor

‎02-13-2024 07:05 PM - edited ‎02-20-2024 04:15 AM

Hi,

 

I have 2 set of users let's say A and B who are part of same group. They are also going to have ITIL access.

 

They don't want to expose their Incidents to other users who are not part of their group. I am aware this can be done using Query business rule but the B set of users should not be able to access other applications rather than their Incidents.

 

I have created a scoped application extending the Incident table in my PDI, I can see the attributes/fields copied to the scoped table but what about the complete Incident lifecycle i.e.) Business rules, Client scripts, UI policy, dictionary override, Notifications etc... are all these need to be created from scratch under the scoped application?

 

Regards,

Vivek

0 Helpfuls
  • 508 Views
2 REPLIES 2

Dr Atul G- LNG
Tera Patron
Tera Patron

‎02-14-2024 04:25 AM

Hi @Vivek13 

 

In this case, create another group for B and give scoped application access.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************
0 Helpfuls

Vivek13
Tera Contributor
In response to Dr Atul G- LNG

‎02-15-2024 07:10 PM

Is it still possible to have the Incident management module as a scoped application and provide that to B users?

0 Helpfuls