How to handle roles in different OUs

[Former Member]

Hi,

Our client has 10+ OUs (Organization Units). Every OU has 3 same user roles, e.g. Data Creater, Data Validator, Data Approver. The client requires that the data created by a 'Data Creater' in one OU must go to the 'Data Validator' of the same OU in a workflow. No other user belonging to the role 'Data Validator' from any other OU should be able to see that data.

any idea how can this be achieved?

One way is to create separate roles for every OU like OU1_Data_Creater, OU1_Data_Validator, OU2_Data_Creater, OU2_Data_Validator...and so on. But then we will also have to create different workflows for different OUs. Any other more practical approach?

Thanks,

-Y

[Former Member]

Hi Yasir,

based on my experience, you don't have to create separate OU for each role

OU[x]_Data_Validator, OU[x]_Data_Creator !

You should create functional roles:

- Data_Validator,

- Data_Creator,

- ....

and also organization roles for each OU:

- OU1

- OU2

....

Then use field from your repository model where you store organizational data (it should be lookup / in my case it was taxonomy) and in role definition assign that role OU1 is abe to read and modify data from that unit (organizational unit filed contains OU1 key).

In this scenario only users that have permission to OUx data can see and modify it.

Hope that helps.

Regards, marcin