Control what your users can access and save time, money, and frustrations. Lock down sensitive data in SugarCRM or SuiteCRM to specific groups or teams. Supports unlimited assigned users, unlimited group assignments to records, custom layouts for each group, login/sudo capabilities and much more.
#36 - SecuritySuite Setting in Custom Module
Hi Jason,
I've the same setting requirement described in the forum link below: http://forums.sugarcrm.com/f6/security-suite-hierarchies-42916/ We are running SugarCRM CE 6.5.7 But I still ran into problems, hope you can assist.
- Created Security Group 'A' for all users with Role 'A1' owner edit rights to all modules.
- Create Security Group 'B' consists of 'user1' and 'user2' with Role 'B1' group read only rights to all modules.
- In Group B, 'user1' has 'Not Inheritable' checked so that he can see 'user2's records but 'user2' won't see 'user1' records.
- Security Suite Settings have all the default settings, plus 'All Modules' defaulted to Group B.
However, both user1 and user2 records' can still be seen by each other. Hope to hear from you soon!
-
"Incredibly useful. It's one of the first features you need. This needs to be part of the core product." - MTP
Read More Reviews
- Most Recent Love from Users
kacsoristvan- damien8105
- anri
- Administrador
- Stefano1
- einkauf2
11 years ago
Hey Peggy,
I've move this case over to the SecuritySuite add-on. The "Not Inheritable" checkbox is only used to determine if a group should not be added automatically to a newly created record if otherwise rules would indicate it should. It seems like that is what you're trying to do, but just pointing that out to be safe.
As far as user2 seeing user1's records it is hard to say without seeing more information. First thing I'd do is to go to user2 and check the permissions grid to ensure that rights really are set to Group. If user2 has multiple roles being applied to the user record it may be getting greater rights than you want. Also, if user2 is able to see a specific record of user1's make sure that the record doesn't have Group B associated to it. (Key point - records need the groups associated to it for group rights to work appropriately)
Hope that helps. -Jason
11 years ago
How do I send you the screen shots? It's a very simple setup. I must be missing something.
11 years ago
Thanks for the pointers. Works brilliantly now! By the way, is there a simple way to specify multi-tiered hierachies where the lower tiers can't access what the higher tiers can?
11 years ago
Excellent! Basically for hierarchies you just have to do a bit of planning ahead. Determine what your lower tier will be first and then create a group for each of those. Then work your way up. Because this module supports unlimited tiers it is really hard to simplify beyond that. Although, I could see an initial setup wizard that gives you some common templates.