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.
#2841 - Automatic add the user's Security Group to a Meeting where the User has been invited
Hi, is it possible to add automatically user's Security Group to a Meeting where the User has been invited?
This will be useful to let the User to see Meetings where he has been invited while in Roles setting the property Meetings.List View is set to "Group"
-
"Couldn't do without it. Highly recommended and I guarantee that you will not find another alternative."
Read More Reviews
- Most Recent Love from Users
kacsoristvan- damien8105
- anri
- Administrador
- Stefano1
- einkauf2
7 years ago
Wouldn't the User be able to see the meetings because they have been invited? Basically should be Owner rights which falls under your Group setting.
7 years ago
Yes, this is what i expected but in SuiteCRM 7.1-7.7 users see meetings where they are invited only in Calendar, not in Meetings module, (nor in Meetings Dashlet).
I found that the inviter has to add the Security Group of the invitee to the meeting, or they have to be in the same Group (so the Security Group is inherited)
7 years ago
Ah yes. I think there is a bug in those versions that was fixed in the 7.7.9 release. Is it possible to upgrade? If not, which version do you need support for?
7 years ago
The customer complaining that has a 7.1.7 You are very kind.
7 years ago
I tried recreating this issue in 7.1.6 (no 7.1.7 download is available) and I couldn't recreate the issue. A user belongs to a group with Group only access to all records. I created a meeting and invited the user to the meeting. Logged in as the user and it shows on the Calendar without having to have the group assigned to the meeting.
7 years ago
My best bet is that 7.1.7 files overrode the logic. Upgrading them to a more recent version should address the issue. Closing this out for now, but feel free to follow up here if needed.