USer /Group Management

Hi All,
We are using camunda in embedded mode. We have organization wise user base, groups, roles, permission, organization hierarchy, all these have parent child relation ship for example group 1 can multiple child.

We want to manage camunda user and group management so that we do not have to replicate and sync data at 2 places. I saw that there is no parent child relationship in camunda group functionality. Could you please suggest what could be best way to maintain these data structure in camunda. We need to have authentication and authorization both.

There is one more case, we need to have more user information for example employee family record which will also be a part workflow, in this case how we can store the information. In the same camunda DB or it should be part of our application DB (please note that we are not changing anything in camunda DB for all application requirement we are keeping the information in another DB (schema) and using it by hibernate api where as camunda is at it i.e. by ibatis api.

All these information is part of workflow for example, we can assign all request to a group or subgroup and then assigned task should be shown to all users in the group.

Hi @Anurag_Tripathi,

I would implement the read only identity service interface to access your user database. Have a look at for background information. The Camunda implementation at may serve as a blueprint.

Hope this helps, Ingo

Hi @Ingo_Richtsmeier ,

Thanks for your reply.
Could you please help us to understand how we can manage group hierarchy? For Example one organization have multiple division->department->section. Based on selection of department or section all workflow request will be assigned to any user of the department or section.

Hi @Anurag_Tripathi,

from my point of view it’s a business decision how to handle your hierarchy. You have to map all groups into a flat list.

This could be done with using only leaf groups. Or you could handle the intermediate groups as well and find all users, who belongs to one of the dependent groups.

But without internal knowlegde of the organisation tree, it’s hard to judge.

Hope this helps, Ingo


Thanks for your reply.

I have done it by type attribute of a group. Parent group will have root as a type. all subgroup (which is a group it self will have type = parent’s group id.

I hope it should work, what is your suggestion on handling organization hierarchy in this way?

not sure how helpful this is for other people, but you sir, have helped me a lot! thanks for the amazingly helpful links and your info. i wanted to know if you don’t mind me asking questions? thanks

1 Like