Hello @PriyanshiVerma1 ,
What you're asking is doable, but just wanted to say upfront that what @Ankur Bawiskar suggested (creating a custom role and assigning it to your group) is actually the cleanest and most ServiceNow-friendly way to go about it. It’s quick, easy to maintain, and follows best practices.
That said, if you're not comfortable going with the custom role route, or you have a specific reason to stick with group-only control — there is another way you can try using a Business Rule on the module.
I came across a similar use case in a community discussion a while back, and here's the gist of how it works:
-
Go to the sys_app_module or sys_app_application table
-
Create a "Before" Query Business Rule
-
Use this kind of logic:
👉 Just replace 'XYZ' with your actual group name, and make sure to plug in the sys_id of the Interaction module you're trying to hide.
What this does is basically filter out the module from the left nav for anyone who isn’t in that group (or admin), even if they have the interaction_agent role.
📌 Here’s the original post I found helpful on this — Hide Application or Module Based on Group.
It’s a bit of a workaround, but it should get the job done if the role-based way doesn’t fit your case.
Let me know how this works for you.
🔹 Please mark ✅ Correct if this solves your query, and 👍 Helpful if you found the response valuable.
Best regards,
Aniket Chavan
🏆 ServiceNow MVP 2025 | 🌟 ServiceNow Rising Star 2024
