Hi Community,
I have this scenario below.
I want to give record permission per Area, I have 100 plus areas, so basically i need also to maintain all these areas as organizational role to assign the role properly. Now these areas are not fixed, it is changing from time to time. Another new area record might be added on the next day, so we need again to manually add this new area as a new organizational role. Also we need to add the users under this newly added added organizational role.
Any suggestion what could be the best approach for this scenario? is it good practice to maintain so many organizational roles? in my case it will be 100 plus and counting.
Like
Hi Fulgen,
The suggestion is to a new column to SysAdminUnit table with link to Area. So whenever the new Area is added to the system, system will automatically check if there is a role with this area and if not - create a new role. Also, I believe when you are adding users to the role, you are following some logic (e.g. user.Contact.Area = area) so after this operation you can also automatically add users to that role.
Please note that it is a complex task so will have to think about structure and the way you want to run this procedure. If the record is added in the UI you can handle it by business process for example, but if areas are created from some kind of integration - you would need to come up with different approach depending on the integration that you are using. The structure of organizational roles is also important. I suggest you to create a new role 'Area roles' and when you are checking if the role exists, or creating a new role - this role should be the parent role.
Regards,
Dmytro