Training & Accessibility

DocuSign User Training 

After completing these courses, you may want to bookmark these to refer back to them regularly. 

DocuSign Introductory User Training from Berkeley (optional)

DocuSign Department Admin Training 

DocuSign training for Department Administrators happens after they have signed the  MOU and have been provisioned as an Account Administrator on the UCB DocuSign campus Demo account.

Here are those training materials:

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. Please email for assistance, we're always happy to work with you.


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: 

More links for working with Accessibility in DocuSign: 

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

When taking a paper based form, or a PDF that was forwarded via email for signature, and transitioning it into DocuSign with built in workflow for back and forth signing between parties, there are some best practices to adopt. Using automatic signature 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. 
  • Be certain that DocuSign is being used because the business process clearly needs a legally binding or contractually required signature. 
  • If the business process really does need binding signatures, 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. 
  • Is your form user-friendly? Research shows that a linear form in which the fields that need completing (including signatures) are intuitive and easy to find.  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 them to the live, Production environment.