UCLA Samueli School of Engineering operates under a licensed DocuSign tenant within the main campus DocuSign system. Below are important details for those needing access to DocuSign services.
If you need a DocuSign account to send documents for signature (envelopes) or to create templates or PowerForms, please note:
DocuSign accounts are not required to sign documents—any recipient can sign without a login.
To request an account under the Engineering DocuSign tenant, your department head must email help@seas.ucla.edu to initiate the process.
By default, new accounts are granted basic sending permissions. If you need access to create Templates or PowerForms, please specify that in the initial request.
If you've created a free DocuSign account using your @seas.ucla.edu email, you will need to switch to the official Engineering tenant:
Log in to DocuSign.
Click your profile image (top-right corner).
Select the UCLA - Samueli School of Engineering from the account switcher dropdown.
Creating a DocuSign account tied to a generic departmental email address (e.g., hr@seas.ucla.edu) is generally not permitted due to current UCLA policy:
All DocuSign accounts at UCLA are federated via Shibboleth, the campus Single Sign-On (SSO) system.
Generic emails are not linked to UCLA Logon credentials and cannot authenticate via SSO.
Campus IT strongly discourages the use of shared accounts for security, auditability, and compliance reasons.
Request an Exception (Not Guaranteed)
In rare cases, we can help submit a request for a non-SSO (non-federated) DocuSign account. This requires:
A strong justification for why a generic account is needed.
An explanation of how access will be secured and monitored.
Please note: Campus has become increasingly strict and may deny such requests.
Use Envelope or Folder Sharing
If multiple users need access to documents:
Create the PowerForm or envelopes using an individual's account.
Use DocuSign’s envelope sharing or folder sharing to grant access to others.
This maintains user-level traceability for compliance.
Redirect Notifications
Use an individual DocuSign account for sending.
Set up notification forwarding (via CC or BCC) so completed documents are also sent to a generic departmental inbox.
🔹 Student Worker Accounts
Student workers can be granted DocuSign access, but there are a few important considerations:
Accounts must still be tied to individual users and authenticated via UCLA Shibboleth using their UCLA Logon ID.
Student employees should only be granted the minimum permissions necessary for their duties (e.g., sending envelopes, not creating PowerForms or templates unless required).
Departments are responsible for:
Submitting the account request (via the department head to help@seas.ucla.edu)
Revoking access when the student’s employment ends or their responsibilities change.
If the student has already created a free DocuSign account with their @ucla.edu or @g.ucla.edu address, they will need to switch to the Engineering tenant via the account switcher (click profile image in DocuSign > switch account).
SEASnet typically does not grant DocuSign accounts to student workers, primarily because we are not always notified when a student leaves their position. However, in certain cases, student workers may be granted access if justified. If so, there are a few important considerations:
Accounts must still be tied to individual users and authenticated via UCLA Shibboleth using their UCLA Logon ID.
Student employees should only be granted the minimum permissions necessary for their duties (e.g., sending envelopes).
Departments are responsible for:
Submitting the account request (via the department head to help@seas.ucla.edu)
Revoking access when the student’s employment ends or their responsibilities change.
If the student has already created a free DocuSign account with their @ucla.edu or @g.ucla.edu address, they will need to switch to the Engineering tenant via the account switcher (click profile image in DocuSign > switch account).