DocuSign Introductory User Training For New and First Time Users
- DocuSign User Training Beginner training for all DocuSign Users, including Department Administrators
DocuSign Department Admin Training
DocuSign training for Department Administrators happens after they have signed the MOU and before they are provisioned as an Account Administrator.
Here are those training materials:
- Department Account Administrator Training - take the first 3 courses, but NOT the Auditing course.
- Quick Start Guide: Department Account Administrator Quick Start Guide
- How to Add and Close User accounts in DocuSign
DocuSign User Training
After completing these courses, you may want to bookmark these to refer back to them regularly.
- Getting Started as a User Basic guide covering most Department User activities
- How to Create a Template
- Take an Instructor led class on Templates from DocuSign
- How to Create a PowerForm
- How to Create a WebForm
- How to use Bulk Send
- Learn to use Advanced features and functions for Users in DocuSign, view a self paced course, or take an instructor led class from DocuSign instructors
Accessibility
It is important that your documents are accessible to those with different abilities. To make sure you're creating accessible "source documents" (a Word doc, Google doc or PDF document) your original layout must be accessible before you import it into DocuSign for signature workflow.
Steps to incorporate accessibility:
- Start Here: Review this 10 minute video about making Word and Google Docs Accessible in DocuSign
- We recommend a Microsoft Word Document or a properly tagged PDF/UA doc
- Use Tooltips for Form Fields. This is critical hover-over text to describe the contents of the field
- Checkboxes and Radio Buttons must have a named value
- Account Administrators should NOT disable the "Select a Style" signature adoption method. This makes it more difficult for screen readers to allow signature options for the Adopt and Sign signing step
More links for working with Accessibility in DocuSign:
- Take a Berkeley class on Accessibility - this is highly recommended
- You can review and bookmark Berkeley's Accessibility Website here
- DocuSign.com/accessibility for more information
- DocuSign Accessibility Overview
- Sending Accessible Envelopes
- Optimizing Accessibility in DocuSign for Sending
Use these resources to create an accessible PDF, and accessible Google Docs, as well as accessible Word documents
From Paper or Email to Automatic Signature Workflow
Using DocuSign for automatic workflow requires re-visioning your process, planning it out, and most importantly, building and testing your DocuSign Template.
- Review and revise your current paper-based business process to optimize it for the new electronic signature process. If you want help with this, email us at esignatures-support@berkeley.edu to request to meet with us. We don't recharge, and we're happy to help get you started!
- Be certain that DocuSign is being used because the business process clearly needs a legally binding or contractually required signature. If you don't require a legally binding signature, use Google Forms, or Adobe PDFs.
- Double check that you are requesting the minimum number of signatures actually needed. Sometimes, instead of signing, viewing (receiving a copy or cc) is all that’s needed when previously you used to collect signatures in a paper-based process.
- Confirm you really need to collect only the data you require – is there less sensitive information you can use/collect instead? Or even less information?
- If you must collect P3 or P4 data, you MUST have a compliant storage solution for that data per University Security policy. Email your form to security-assessments@berkeley.edu to ask what classification of data your form collects.
- Is your form user-friendly? Keep it simple and logical.
- Are you using the Berkeley/department/unit’s brand appropriately?
- You must first create and test your forms and workflow in the Demo environment prior to moving to the live, Production environment.
Technical Support from DocuSign
Any API configuration from another system to DocuSign (an "Inbound Integration") or any API configuration from DocuSign TO another system (an "Outbound Integration") must be approved by the ISO, and, the eSignatures team must have a copy of this approval. APIs cannot be configured by Users or Departments with out our help. You will need to email esignatures-support@berkeley.edu for assistance, we're always happy to work with you, and we do not recharge for this support.