COE Security Policy Not Working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2025 07:01 AM
I have created a COE security policy identical to the below on each of our COE tables. When I impersonate a user in one of these groups to test the policies, the user can still see all cases. What am I doing wrong?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2025 10:11 AM
This is the only COE security policy that is active. I'd really rather not go down the ACL path as that more complex. This seems like a perfect use case for COE security policies.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2025 05:47 PM
Ok. So you are saying this is the only COE security policy you have in your instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2025 10:39 AM
The security policy I have in the first screenshot, I've created the same rules for each COE we use. Those are the only active policies.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2025 10:53 PM
Hi @tworzala ,
Here is the solution for the query.
You have to create separate COE Security policy for each group you have, and no need to add condition for 'assignment group dunamic'.
for example you can check below snip. that gives only access to "HR Tier 2" group members if the HR Case assignement group is HR Tier 2". In the same way you can create COE Security policy for each group by adding group name to condition and Group list.
If my response help you to resolve your query, please mark it as Helpful and accept the solution.
Thank You!