Overview 

The order of signatures on a document used within Experiential Learning Cloud will determine who can "view and sign" the form, or what 'route' the form will take in the assignment completion process

Who should sign and in what order? 

The order of the signatures on a form will determine the route the assignment follows once it has been started or "submitted". The user completing the form should be the first signer listed on the form. For example, if a form is completed by a student within an assignment, and it is signed in this order:

1. Student

2. Site Supervisor

3. Course Supervisor

Then the student will typically complete the form's fields and sign it. They will then click the submit button and the form will then be routed to the selected site supervisor for review and signature. Once the Site Supervisor signs the document, it will then be sent to the Course Supervisor for final review and signature. Once the final signature listed has been completed, the document will lock and the assignment will be marked complete. If you are a course supervisor but not a signer on the form you can add yourself as a reviewer to view the form before it is locked.

How do I change an assignment's routing? 

There are a couple of ways to change the route an assignment takes in the review/completion process.  

• Change the order of the signers.

  • If a site supervisor signs a form before a course instructor, and you swap the order, the course instructor could review, sign, or request changes before the site supervisor can view the form. To change the order of signers, submit a support request with the form name and the new desired signing order.

  • NOTE: If you have the signing order changed on a form that is being used in an active course assignment, you will need to open the assignment and click the Refresh Signers button in order for the form to reflect the requested changes.       

  

• Change the signer tags on the signature field within a form.

  • Typically, a signature field labeled 'Site Supervisor' can only be signed by users with the Site Supervisor/Field Instructor role. This means only users with that role (who supervise the student submitting the document) will appear as submission options.

    • You can request a signer field have more than one role tag or you can have the tag changed to a different user type.

• Make a signature field optional, which allows the user to skip that specific submission option.

• Administrators with the Program Administrative Functions Plus + role also have the ability to skip required signature steps if needed.