- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 08:45 AM
We have interaction table and it's module. In the Interaction application menu interaction_agent and admin role is added. so the persons are having these role will be able to see the interaction table.
My requirement is that I want make it available for the users who are member of XYZ group. If they are not a member of XYZ group and having intercation_agent role stiil they should not be able to access interaction table.
So I want make it strictly available only for the members of XYZ group.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2025 04:15 AM - edited 06-30-2025 04:32 AM
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:
if (!gs.getUser().isMemberOf('XYZ') && !gs.hasRole('admin')) {
current.addQuery('sys_id', '!=', 'your_module_sys_id_here');
}
👉 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 09:00 AM
Edit module ->Add the role
->the roles (or groups via roles) that should see the module.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 09:08 AM
Unfortunately the left nav modules can only be driven by role and not by group membership.
You can do this
1) create a custom role and give that to your group so group members get that role
2) then give this role to the left nav module and application menu
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 09:22 AM
Yes we can do it but the OOB ACL which are giving access to the application menu. what about those?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 08:08 PM
you can give that custom role to the application menu
So users with only that role will see the application menu
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader