Signature Process Flows empower you to assign the right members, teams, or logic according to your project requirements. By following the guidelines below and keeping the important points in mind, you can efficiently manage and streamline your signature process policy. Signature flows can be applied to projects and are reflected throughout experiments of the project. As the signature process progresses, relevant users are notified.
(Note that a user cannot sign twice in a signature process)
Accessing Signature Process Flows
System admins hold the ability to design signature flows by heading to the account settings and clicking on the Signature Process tab. There all available signature flows created will appear as well as the option to add a new flow.
Applying Signature Flows
Signature flows will be available to set at the project level and can be applied through permissions. The flow applied will trickle down to all new experiments within the project.
Designing a Signature Flow
When designing a new flow, you can add up to five additional steps to the signature process, apart from the initial signature and witnessing step(mandatory).
In each step the following settings are required:
Intended meaning of the signature (reflected by the Role of Signer)
Teams and/or members with signing permissions in the step
Number of signatures required to proceed to the next step
(default is one, maximum is three, and the number of signatures required can not exceed the number of members set at each step).
Consider Team Assignments
Signature flows applied to projects are non-editable. Therefore we recommend using teams to assign members to specific steps as they can be updated and changed overtime. Assignment of individual members to steps should be limited because individuals cannot be edited once the flow is applied.
Best Practice Example
Consider a scenario where each experiment within a project requires only QA approval prior to being witnessed. Instead of creating a unique custom signature process for every project, it is recommended to include a step in the signature flow that involves assigning the QA team. By doing so, only the QA member assigned to the specific project will receive notifications and have the ability to provide signatures, while the other QA team members will not be notified or have the capability to sign. This approach ensures correlation between assignment within a project and signature responsibilities.
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. |