General Questions
SF State Adobe Sign emails will always come from the following email address: adobesign@adobesign.com. If you are uncertain of the email’s authenticity, we advise you to first log into your Adobe Sign account to locate and access the transaction from within the SF State-Adobe Sign domain. If the transaction cannot be located, we strongly recommend reporting the suspicious activity to Adobe Sign.
For guidelines on how to identify and report suspicious Adobe Sign activity, please refer to Adobe Sign's guidelines on Notifying Adobe of Security Issues and Report Abuse links.
For more information about phishing, please refer to ITS’ phishing guides:
Clearing your browser's cache can fix issues with websites loading incorrectly or displaying outdated information. The cache stores website data to speed up future visits, but it can sometimes become outdated or corrupted. Removing it allows the browser to load fresh content, often resolving these problems.
For step-by-step guidance, please refer to the following pages:
Adobe Sign is compatible with the latest versions of major web browsers, including Google Chrome, Mozilla Firefox, Microsoft Edge, and Safari. These browsers support the necessary security protocols and features required for optimal performance.
Learn more about the System requirements for Adobe Acrobat Sign.
Adobe Sign allows users can customize their email notification settings. Users can choose which types of notifications they want to receive and how frequently they are sent, giving them control over their communication preferences.
For more information, please refer to the Configure personal event/alert notifications page.
Accounts and Access
Some individuals may have previously created a personal Adobe Sign account using their @sfsu.edu or @mail.sfsu.edu email address. If this applies to you, you will be prompted to choose between a Personal Account and a Company or School Account when signing in to Adobe Sign. To ensure proper access to the SF State Adobe Sign environment, always select Company or School Account. This ensures you can view and manage agreements related to official university business.
For step-by-step guidance, please refer to the Sign in to your company or school account page.
Signing and Completing Agreements
Adobe Sign offers a variety of recipient roles to support flexible workflows, including Form Fillers, Signers, Acceptors, Approvers, and Delegators. Each role defines how a recipient interacts with the agreement, whether by signing, reviewing, filling out fields, or delegating responsibilities to the appropriate party.
| Recipient Type | Role and Responsibilities |
|---|---|
| Form Filler |
A Form Filler is a recipient who is required to enter data into an Adobe Sign agreement but is not required to provide a signature. All form field types, including signature fields, can be assigned to a Form Filler if needed. |
| Signer |
A Signer is a recipient who is required to sign their signature on an Adobe Sign agreement. Each signer must have at least one required signature form field assigned to them. If the system does not detect a signature form field for the Signer, it will automatically generate a signature block at the end of the document. |
| Acceptor |
An Acceptor is a recipient who is not required to provide a signature on an Adobe Sign agreement. They are expected to review and acknowledge the document. However, if form fields are assigned to them, they will be required to complete those fields. |
| Approver | An Approver is a recipient who is not required to sign an Adobe Sign agreement. However, they must review the agreement and enter their name so that the agreement can be routed to the next recipient. If there are any fields assigned that are marked as required, the Approver must take action on those fields. |
| Delegator | A Delegator is a recipient role that allows the individual to reassign their signing or approval responsibility to someone else. This role is used when the Delegator is expected to determine and reassign the Adobe Sign agreement to the appropriate person for signature or approval. |
For more information, please refer to the Allow various recipient roles page.
Initiators can make certain corrections to an in-progress agreement for recipients who have not yet signed. This includes:
- Add, delete, replace, and reorder (delete then add), and reorder documents.
- Add, delete, replace, and reorder form fields.
- Edit field properties such as default values, participant assignment, and validation rules.
- Update values applied to a Prefill field if incorrect information was inserted.
However, modifications are not allowed if any of the following conditions are met:
- The agreement has already been signed, approved, or delegated by the assigned signer or approver.
- The agreement includes a digital or written signature.
- The agreement was initiated from a custom workflow or the Send in Bulk feature.
Learn more about Modify a sent agreement's documents or fields and Allow recipients to restart agreements.
Adobe Sign allows team members to access and act on agreements when another member is out of the office by using features like Recipient Groups, the Delegator Role, and Auto Delegation.
Recipient Groups
For business processes where responsibilities are shared among a defined group, the recipient group feature allows any member to act on an agreement on behalf of the entire group. This helps ensure the agreement progresses through the approval process without unnecessary delays. If you’d like to create a recipient group for your team or unit, you may submit a service ticket.
Learn more about Reusable recipient groups.
Delegator Role
The delegator role can be built into Adobe Sign workflows. The role allows the individual to reassign their signing or approval responsibility to someone else. This role is used when the Delegator is expected to determine and reassign the Adobe Sign agreement to the appropriate person for signature or approval.
For more information, please refer to the Allow various recipient roles page.
The Send in Bulk feature allows initiators to send up to 1,000 transactions using a pre-configured agreement in Adobe Sign. Each agreement is treated as an individual transaction, allowing for separate tracking, status updates, and record-keeping. There are two methods to add the recipients to the agreement:
- Manual Entry: The initiator manually types or pastes the recipients' email addresses.
- Comma-Separated Value (CSV) file upload: The CSV file is used, where each row represents a recipient and each column corresponds to a form field in the agreement.
For more information, please refer to the Overview of Send in Bulk page.
The Initiator can cancel an agreement at any time. Canceling an agreement immediately stops the transaction in its current state and cancels the signing process for any remaining recipients. During the cancellation process, the initiator has the option to provide a reason and notify all recipients. Once canceled, the action is irreversible, and the agreement will be moved to the Canceled category on the user's Manage page.
Recipients have the option to decline an agreement if they do not wish to sign. Declining stops all reminders and cancels the agreement within the Adobe Sign system. A declined agreement cannot be restarted, and a new agreement must be created by the Initiator.
Adobe Sign is the approved tool for all University-related business processes that involve SF State employees and external parties, with all signers required to operate within their designated signing authority. For agreements that involve external parties, please refer to the Security Matrix and apply the recommended security controls based on the assessed risk level of your documents.