Performing Multiple Roles Based on Access Rights – Dhanya S

Integration Of To-Do With Odoo Calendar – Subhashree
April 18, 2018
Storytelling In Business Analysis – Venkatesh P
April 18, 2018

Performing Multiple Roles Based on Access Rights – Dhanya S

Users are allowed to perform tasks based on the access rights granted to them, but what if the same user is given more than one role. What if the same user is the User, Manager, Follower, etc. in various projects? Now this gets a bit tricky.

Scenario:

A user should act as a Project Manager in one project where he has the complete access rights and is considered as the Owner for that project whereas, in another project the same user has restricted access to the project information. If he is one of the project team members, he cannot delete, approve or close the project and in another scenario when the same user is a follower, he is only allowed to view the projects to keep a track of the progress.

When the requirements are as complex as the above scenario, the most challenging part is to hide data based on the roles. The project manager should keep a track of all the team members’ tasks, the team members should be able to view only their task and the followers must only be able to view the task that they’re added to.

Solution:

After a detailed study of the scenario and the requirements, we arrived at a solution. We decided to provide access rights based on the field rather than providing individual roles and access rights. For this reason, all the employees of the company were allotted with some specific rights that are common and depending upon the projects, the roles were allotted. So the actual method is to let the field names to which users are assigned take control of the access rights for each project.

Example:

Let’s consider a scenario where User A is assigned as Project Manager for Project A, whereas he should be one of the team members for Project B and a Follower for Project C.

Now in Project A, User A will be added in the field where the Project Manager’s name has to be filled, as mentioned earlier. The complete authority over that project goes to him whereas in Project B he is added as a team member and that particular field restricts the access rights to only being able to view and edit the tasks assigned to that user.

In Project C, as the User A is added as a follower and the follower field has rights only to view the project, User A cannot make any edits in Project C.

It’s that simple! This concept can be applied across any framework you may be using. A simple worthy idea can overcome even the most tedious of problems!

Keywords: User, roles, multiple roles, admin, manager, follower, project management, task assignment, access rights, project manager

Users are allowed to perform tasks based on the access rights granted to them, but what if the same user is given more than one role. What if the same user is the User, Manager, Follower, etc. in various projects? Now this gets a bit tricky.

Leave a Reply

Your email address will not be published. Required fields are marked *