HI @rwhetsell77 

Not sure if you saw this chart or not but it’s pretty helpful:

Recommendations for Selecting the Restriction Group Type

As you decide which type of restriction group best meets your security needs, consider the following recommendations:

• When you create multiple groups with entities of the same combination of types (for example, suppose that you have two restriction groups that include users and customers), use groups of the same basic type (either A or . (Otherwise, if you were to add the same entity to multiple groups of different types, the result may not be what you expect.)
• To configure the required visibility of entities, you can combine direct and inverse restriction groups of the same basic type (either A or , as was done in the solution of Usage Example 2. Thus, you can combine groups of types A and A Inverse, and groups of types B and B Inverse.
• If you want to hide particular entities from the majority of users, include the entities and the users who should see the entities in a group with direct restriction (type A or B).
• If you want to hide particular entities from a small number of users, add the entities and the users who shouldn’t see the entities to a group with inverse restriction (type A Inverse or B Inverse).               

HI @rwhetsell77 

Not sure if you saw this chart or not but it’s pretty helpful:

 

Recommendations for Selecting the Restriction Group Type

As you decide which type of restriction group best meets your security needs, consider the following recommendations:

• When you create multiple groups with entities of the same combination of types (for example, suppose that you have two restriction groups that include users and customers), use groups of the same basic type (either A or . (Otherwise, if you were to add the same entity to multiple groups of different types, the result may not be what you expect.)
• To configure the required visibility of entities, you can combine direct and inverse restriction groups of the same basic type (either A or , as was done in the solution of Usage Example 2. Thus, you can combine groups of types A and A Inverse, and groups of types B and B Inverse.
• If you want to hide particular entities from the majority of users, include the entities and the users who should see the entities in a group with direct restriction (type A or B).
• If you want to hide particular entities from a small number of users, add the entities and the users who shouldn’t see the entities to a group with inverse restriction (type A Inverse or B Inverse).               

Thanks Kandy, yes, I’ve seen this. What we are struggling with is what seems to be very buggy behavior, never mind it’s supper clunky to manage.

Once you start playing with the Customer Access setup, it seems to mess with the system even when all groups are inactive. You can’t delete once created. The only setup that seems to behave as expected is the inverse.

Have you reached out to support since it’s causing unexpected issues in other areas? 

Hi @rwhetsell77 , hope you are doing well!

Please review the below article and let me know your feedback.

https://www.augforums.com/forums/everything-else/restriction-groups/

Thanks

Yes, I put in a case. It is being actively worked as we speak.

Thanks Chandra! This was definitely helpful but hasn’t solved the buggy behavior that seems to be present.