Different projects can have different requirements when it comes to who should be able to sign or witness the experiments.
In order to address these project-specific signature requirements, and provide a tailored signature process for each project, we have developed a feature that allows the creation of custom-made signature flows.
The signing and witnessing steps (mandatory) can be limited to either a specific member or to the entire team (i.e. all members of the team are allowed to witness).
Your teams should be setup or updated to align with the signature flows you wish to create. Various teams can be created in order to capture different levels of organizational/divisional structures, or distinguish project-orientated teams from disciplinary groups.
Signature process flows
When a signature flow is applied to a project, only members that were defined in that flow will have the option to sign or witness all project-related experiments (even if their role does not include the 'Can witness' privilege).
This also guarantees that other members who do possess the ‘can witness’ permission will not be able to witness experiments that are out of their scope.
A key aspect of the signature process is that the first signature is not part of the flow but rather a trigger to initiate the signature process.
How to create a customized signature flow
Go to the account settings page by clicking on the account name drop-down menu and choosing ‘settings’.
Navigate to the "Signature process " tab and click on ‘Add new flow’ to open the signature 'Flow designer'.
The default signature flow name will include the date and your name. To change the ‘Name’ field, click on the name and change it to an informative name that suggests its content or intended use.
You can add steps to your signature flow or only define the witnessing step (mandatory)
Select the required logic for the flow you are creating from the following options:
Only selected members and/or teams will be granted permission to witness experiments within a project
All members that are assigned to the project i.e., have viewing permission to the project, will be able to witness experiments within that project.
You will be asked to define how many signatures you require at each step if you have added a step to the signature process.
Once you’ve defined the flow, click on ‘Save’ to make it available for selection on the project page.
Default signature flow'Default' signature flow represents the behavior where witnessing priviladge is granted to users by "Can witness" permission as part of their role. 'Default' signature flow content and name is non editable and is the flow set when creating a new project. |
How to apply a custom flow to a project
Once a flow is defined, it can be later applied to a project via the ‘permission’ option found in under ‘More’ menu. To apply a customized signature flow, follow these steps:
Go to the project page
Click on the ‘More’ drop-down menu at the upper right side of the screen.
Click on ‘Permissions’ and select the required flow from the list of existing flows.
Save changes.
All unsigned experiments within a project will be immediately subjected to the selected signature flow.
Where can you see notification regarding signature process?
As part of the signature process, your dashboard will display how many experiments are awaiting signature.
You can also filter your Experiments page to easily find only the experiments that are awaiting signature.
Key Guru Points
|
|