The purpose of this document is to provide distinctions between DocuSign, Softdocs, Power Automate, and explain other possible considerations.
The following services are supported by ITS and are available for campus use:
DocuSign
Primary Purpose: obtain legally binding, “wet”, signatures
Benefits
Supports legal documents
Accessible to non-SU account holders (including parent, vendor and notary)
Things to consider
Only choice for legally binding signature
Document cannot change once it enters workflow
New engagements must be scheduled with ITS
For questions related to DocuSign or to schedule a consultation for DocuSign please submit a ticket with the ITS Service Desk here
Softdocs
Primary Purpose: Student-facing forms for Student Financial Services and Registrar
Benefits
Supports user authentication
Many integrations, including Colleague
Very Customizable
Best option when you need a workflow that someone else will design/build for you
Best first option when you need a workflow that requires acknowledgement of acceptance (for example, reviewed and approved by a Dean or VP) but does not require a legal signature
Things to consider
Significant “hand-coding” means each engagement is a new project
New engagements must be scheduled with ITS here
For questions related to Softdocs, or to schedule a consultations for Softdocs, please contact Madelyn Ringstad (ringstad@seattleu.edu) or submit a project request
Power Automate
Primary Purpose: Self-service automations for Microsoft Office apps
Benefits
Include in our Office suite: installed, configured, ready to use
Supports user authentication
Can be used when you need a basic workflow for Microsoft Office applications, and cannot wait for ITS availability
Available for self-support
Things to consider
Limited free workflow options; advanced workflow require paid “premium” connectors
ITS can offer basic troubleshooting and offer escalation MS Support Channels
For questions related to Power Automate or to schedule a consultation for Power Automate please submit a ticket with the ITS Service Desk here
What else should I know?
“Legally Binding” and “Acknowledgement of Acceptance” are separate concepts. Internal workflows that involve campus members often require acknowledgement of acceptance (can be served by Softdocs and Power Automate) but rarely require a legally binding signature.
University Counsel should be consulted for all items that require a legally binding signature, including contracts with vendors outside of Seattle University.
ITS has a team to design and build Softdocs and DocuSign workflows. ITS can provide basic Power Automate instructions and can escalate issues to Microsoft Support, but does not staff for Power Automate design/build support.
Need additional help? Submit a ticket with the Service Desk here: IT Service Desk Help Center
Related Articles:
/wiki/spaces/TKS/pages/312868873