Training & Accessibility

DocuSign Introductory User Training For New and First Time Users 

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:

DocuSign User Training 

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

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: 

More links for working with Accessibility in DocuSign: 

Use these resources to create an accessible PDF(link is external), and accessible Google Docs(link is external), as well as accessible Word documents(link is external)

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(link is external), you MUST have a compliant storage solution(link is external) 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(link is external)?
  • You must first create and test your forms and workflow in the Demo environment(link is external) prior to moving to the live, Production environment(link is external).

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(link sends e-mail) for assistance, we're always happy to work with you, and we do not recharge for this support.