Security group assigned but not working


#1

Hi,

We’re using Security Suite and we don’t know why but there are some records from a custom module that should have a security group assigned, because in the security suite subpanel that appears in the detail view of the record we can see it, but the record doesn’t appear in the securitygroups_records table and so users who belong to that security group can’t access this record.

The Security Suite configuration is:

  • Additive Rights: Yes
  • New User Group Popup: Yes
  • User Role Precedence: Yes
  • Inherit from Parent Record: Yes
    The other options are not marked.

Does anyone know what is happening and how to solve it?

Thanks in advance,

Pat


#2

Pat,

did you check sugarcrm.log on errors caused by securitygroups queries?

Val


#3

Hi Val,

I have checked sugarcrm.log after trying to access the record from the user that can’t see it and also after re-assigning the record to the security group, but I don’t see any errors on the log related to securitygroups queries. I can paste here some queries from the log related to securitygroups if you want, but they are a bit complex.

Should I do any other action to get something in the log that can enlight us?

Thanks in advance,

Pat


#4

Pat,
Let me check if I understood the problem correctly:
Your module is under ACL control (=> you did a repair role after adding the module to your CRM)
The module knows about SecurityGroups since the SecurityGroups subpanel appears in DetailView.
Some of the records do not display any securitygroups entries in this subpanel.
You noticed that these records do not show up in securitygroups_records tabel.

When/How are SecurityGroups assgined to your module record?

And which CRM in which version do you have in use?

Val


#5

Hi Val,

Finally we found that the problem was that when installing Security Suite in a custom module, we edited the custom/metadata file related to the relationship Security Suite - custom module in a wrong way. We put our custom module as the lhs_module instead of placing it as the rhs_module. That was the reason why records were stored in the database in a bad way (record_id and securitygroup_id were turned in securitygroups_records table) and so the groups we were seeing in Security groups subpanel in the detail view of the record were not really assigned.

Thanks for your help :slight_smile:

Pat


#6

Great, thank you for sharing.