Currently, all the users in our company are able to see the processes in ProMapp, but we need to restrict the visibility depending on region. Based on the research that I've made, I've seen the processes can be accessed based on group, but we need to give visibility to users to multiple groups, so they can see some processes that are visible currently to the other region. Can we restrict users to see only specific processes based on region?
Solved
Process User access
+1Best answer by EvgeniosE
Either way, the separation depends on the type of separation you want to achieve and how you would like to maintain things in the future. Since you are mentioning region I would also ask about the scale of the region (i.e. is it West-US vs East-US or US vs EU). The most clear cut way would be to have a second Process Manager tenant and share any common processes using the embedded processes capability. That would also handle any regional separation for data sovereignty purposes.
Now if your regions are in the same data region (e.g. both located in the US), then you could use roles (e.g. create “Region Current” and “Region New”). You can then separate processes in sub-groups and define which Role needs to view which sub-group. I would suggest doing this at the sub-group level, due to the access inheritance of the process groups.
It might be worth setting up a call via your Account Manager if you want to explore some more specific set-ups.
- Nintex Employee
Hello
+1I don’t do that yet. We used to have users from one region only and all of them had access to processes. Now, we work with people from another region and we want to give them visibility to some processes, but not all. That’s why I thought to use region as criteria, but I don’t know if it’s applicable in ProMapp or there’s another way to give them access.
- Nintex Employee
- Answer
Either way, the separation depends on the type of separation you want to achieve and how you would like to maintain things in the future. Since you are mentioning region I would also ask about the scale of the region (i.e. is it West-US vs East-US or US vs EU). The most clear cut way would be to have a second Process Manager tenant and share any common processes using the embedded processes capability. That would also handle any regional separation for data sovereignty purposes.
Now if your regions are in the same data region (e.g. both located in the US), then you could use roles (e.g. create “Region Current” and “Region New”). You can then separate processes in sub-groups and define which Role needs to view which sub-group. I would suggest doing this at the sub-group level, due to the access inheritance of the process groups.
It might be worth setting up a call via your Account Manager if you want to explore some more specific set-ups.
+1Hi Evgenios,
I’m talking about 2 different geographic regions: EU and ASIA, but already answered my question. I will get in touch with my account manager for more specific set-ups.
Thank you!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.