Documentation › Private phases and steps
Private phases and steps
Inside shared work, a work unit can keep a part to itself. For example, in the shared “Recruitment” process, the “Salary negotiation” phase stays private to HR.
What it is for
The others know that the process is waiting and when it should move on, without seeing what happens in it.
In the process editor
- Open the block
Edit a phase or a step.
- Choose the work unit
In the Keep private to field, choose the work unit. Everything inside a private phase is private too.
- Save
The process instances started afterwards inherit it.
In a process instance
Open the task, then click Make private to keep it to your work unit, or Make visible to open it again. This choice only applies to this process instance, and is reserved for the people of the work unit concerned.
Who sees what
- In full: the members of the work unit, the people assigned to the task, and the administrators of the organization.
- The others see a Private step, handled by… block with its status. They see neither its name, its form, its attachments, its comments nor its activity.
- The values a private task sets are masked for them, including in the documents they generate.
- E-mails: the values a private task sets never leave in an e-mail of another step, whoever prepares it, because its recipients may be outside the work unit. The
{{Name}}placeholder stays as it is in the generated body and attachments. Only an e-mail step kept private by the same work unit shows them. - API calls: a call to an API sends the real values, since the process designer chose the service that receives them.