In the 'Recipients' field of a new request, set the signature flow/approval for the request by typing the list of recipients separated by:

• "()" (Brackets). To indicate a set of users who can sign in any order.
• "," (Comma). To distinguish between separate signature lines, or users within a parenthesis.
• ">" (Symbol greater than). To indicate cascading signature flow; the recipient (or recipients in case of a group in brackets) to the left of > must sign/approve before the recipient (or recipients in case of a group in brackets) to the right.

Example: (User 1 > User 2), User 3. In this case, there are two signature lines; User 1 and User 3 can already sign the request, while User 2 can only sign after User 1 has signed.

• || (or). To indicate a signature flow in which only one of the recipients has to sign/approve.

Example: User 1 || User 2. The request must be signed by User 1 or by User 2. As soon as one of them signs the request, it will be finalised without the other recipient having to take any action. On the other hand, to indicate the type of action (signature or approval) to be carried out by a recipient, add the following just after the recipient:

• (F). To request signature. If no action is indicated, electronic signature is requested by default.
• (VB). To request approval.

The difference between "signature" and "approval" is that in "approval" there is no electronic signature embedded in the signed documents, and it has the same legal validity as a handwritten signature. A classic use case is that of a person who reviews the documents to be signed by his immediate superior. Example: User 1 (VB) > User 2. In this case, User 2 would only be able to sign after approval by User 1. The "recipients" field use predictive characters: as the user types, suggestions are offered to choose from a list of recipients matching the text being typed.

This list of suggestions includes:

• Users: the system searches for a name/surname or email to propose the addition of a specific user. If there is more than one organisation in the form, the organisation's name will also be displayed and can also be searched for using this field.
• Groups: to add ALL users belonging to the selected group (if groups have been registered in the system by the administrators).
• Position clusters: to add ALL users belonging to the selected position (if positions have been added to the system by administrators).
• Flows: to add the complete signature circuit defined for a specific flow. Other sections on this site explain how to create customized signature flows to be reused on other occasions. If a personalised flow called "Approval of acts" is created, the "recipients" field will suggest the use of this flow when introducing characters such as "apro", for example.

Below the "recipients" field there are two options: 'save flow' and 'Preview flow'. The 'Save flow' button allows to quickly get to the option of creating customised flows, starting from the flow on the screen. The 'Preview flow' button displays a graphical representation of the signature flow in the recipient box.