Just occasionally you may have a project that is extremely sensitive, maybe HR are preparing some Organisation changes or for new project that is internal use for a certain department/s.
If you have had this situation, how did you handle access?
Yes, we have our own solution however, it would be good to know if anyone has something that is very elegant or simpler 😉
Alexander Cherednichenko on
I would say there are basically two strategies here:
1. Separate models and object definitions
Keep the sensitive models in one folder with restricted read access, and keep the object definitions in another folder that remains visible to the wider audience.
In this setup, users will not see the sensitive models themselves, but they can still see and reuse the relevant object definitions, for example, roles, positions, systems, etc., in other process models.
2. Filters/method configuration
The second approach is using filters. In most cases, this is used either to hide specific model types or, more often, to hide certain object types or attributes.
For example, this may be relevant for risks, DoA / delegation of authority objects, KPI values, financial values, salary-related information, and so on.