Solved

Need better understanding of how to set up Customer Access

  • 19 September 2023
  • 6 replies
  • 51 views

Userlevel 3
Badge

We are attempting to use “Customer Access” functionality to restrict salespeople from seeing accounts other than their own.

We are really struggling to set up an “A” group as that would be the easiest way to control it. “A” inverse works perfectly, but that would create more work when new customers are added.

Just a general understanding of how “A” vs “B” is meant to work. Totally understand how the inverse works.

icon

Best answer by ChandraM 19 September 2023, 15:47

View original

6 replies

Userlevel 7
Badge +9

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

Userlevel 7
Badge +15

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 B). (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 B), 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).               
Userlevel 3
Badge

        

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? 

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

Userlevel 3
Badge

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 B). (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 B), 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.

Userlevel 7
Badge +15

        

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? 

Userlevel 3
Badge

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

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

Reply


About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved