What You Will Learn

This guide provides step-by-step instructions on configuring Adobe Acrobat Sign for WorkEx to streamline work experience agreement workflows in schools. By the end of this guide, you will be able to:

• Set up account management, security, and workflow automation for efficient agreement processing.

• Integrate Adobe Sign with Microsoft Power Automate and SharePoint for automated tracking and storage.

• Configure web forms, recipient verification, role-based permissions, and email settings to ensure compliance and consistency.

• Apply best practices for security, encryption, and controlled document sharing to protect sensitive data.

Intended Audience

This guide is designed for IT administrators, and administrative staff responsible for managing Adobe Sign settings for work experience agreements. It is also useful for decision-makers overseeing digital transformation and document automation in schools.

Creation Date: Mar 04, 2025

Created By: Brahim Stewart

​

​

Browse to the Adobe Sign Home page

1. Click on Account

Click on Account in Adobe Sign to open the main account management dashboard, where you can configure settings for your school’s Work Experience Agreement process.

2. Open Account Settings

Click on Account Settings to access configuration options for managing user roles, permissions, and workflow automation.

Global Settings

The Global Settings section in Adobe Sign contains account-wide configuration options that affect how agreements are created, sent, signed, and managed. These settings help schools standardize workflows, enforce security measures, and control document handling for Work Experience Agreements. By properly configuring Global Settings, schools can ensure that agreements are processed efficiently while meeting compliance and administrative requirements.

3. Open Global Settings

Click on Global Settings to configure settings that apply to all users and agreements within your school’s Adobe Sign account.

4. New Recipient Experience

Check the box for “Enable the modern recipient experience for signers” in the Global Settings section.

Purpose:
This setting ensures that recipients signing agreements have access to the latest Adobe Sign interface, which improves usability and provides a smoother signing experience.

Recommended Settings:
✔ Recommended – This should be enabled for better user experience, especially for students, parents, and employers signing Work Experience Agreements.

5. Web Forms

Web Forms allow users to create self-service agreements that can be accessed via a shared link instead of being sent individually. This is useful for schools handling multiple Work Experience Agreements, where students, parents, and employers can access a standardized form without manual email invitations.

---

Settings Explained:

• Allow the use of Web Forms – Enables Web Forms, allowing agreements to be completed via a public or shared link instead of requiring direct email invitations.

• Allow CCs within Web Forms – Allows additional recipients (e.g., school coordinators) to be copied on the form submission.

• Allow PDF preview of Web Forms – Provides a preview of the Web Form as a PDF before signing, helping users confirm details before submitting.

• Require an email address in the signature block of Web Forms – Forces users to enter an email address when signing, ensuring records can be tracked.

• Require Signer to verify their email address – Adds security by requiring signers to confirm their email before proceeding with the form.

• Allow additional participants – Lets multiple people sign the form if needed (e.g., both student and parent).

• First Signers must validate their email before accessing Web Forms – Ensures the first signer confirms their email before gaining access, preventing unauthorized form access.

• Allow recipients to save their progress and continue later – Allows signers to save their progress and return later if they can’t complete the form in one session.

• Disable Signer reauthentication on accessing the web form from an emailed link – Removes the need for signers to log in again when reopening a form link from an email.

• Allow editing agreement name – Enables users to modify the form title before signing, which can be useful if different agreements need custom naming.

---

Recommended Settings:

✔ Allow the use of Web Forms – This is essential for enabling online Work Experience Agreement forms.
✔ Allow PDF preview of Web Forms – Prevents errors by letting signers review the form before submission.
✔ Require Signer to verify their email address – Adds security by confirming the signer’s identity.
✔ First Signers must validate their email before accessing Web Forms – Ensures only authorized users access the form.

⛔️ Required Setting:✔ Enable Power Automate workflows within Acrobat Sign – This is required for automating the Work Experience Agreement processes.

6. Power Automate Workflows

Power Automate Workflows allow Adobe Sign to integrate with Microsoft Power Automate, enabling automated processes for agreement handling. Schools can use this to automate sending, tracking, and storing Work Experience Agreements without manual intervention.

---

Settings Explained:

• Enable Power Automate workflows within Acrobat Sign – Activates Power Automate integration, allowing automation of Adobe Sign processes such as sending agreements and tracking completions.

• Allow users to create Power Automate workflows within Acrobat Sign by default – Permits users to create their own automation workflows within Adobe Sign without requiring admin approval.

• Allow users to enable this feature – Lets individual users activate Power Automate workflows if they have access.

• Terms Agreement – Enabling this feature requires agreeing to Adobe’s Terms of Included Entitlement, Limits on Use Capacity, and Microsoft’s terms.

---

Recommended Settings:

✔ Enable Power Automate workflows within Acrobat Sign – This is highly recommended for automating Work Experience Agreement processes.
✔ Allow users to create Power Automate workflows within Acrobat Sign by default – Recommended only for IT administrators and designated staff managing agreement workflows.
✔ Allow users to enable this feature – Enable only if staff members are trained in Power Automate.

⛔️ Required Settings:✔ Allow creating library templates and reusable form fields – Essential for maintaining a standardized Work Experience Agreement format.✔ Allow Users to share library documents to account – Recommended for efficiency, allowing staff to access pre-approved templates.

7. Library Documents

Library Documents allow schools to create and store reusable agreement templates that can be shared across staff members. This is useful for standardizing Work Experience Agreements so that all students, parents, and employers receive a consistent document.

---

Settings Explained:

• Allow creating library templates and reusable form fields – Enables users to create standardized document templates that can be used multiple times without needing to manually upload a new file for each agreement.

• Allow Users to share library documents to account – Permits users to share saved templates with others in the school’s Adobe Sign account, making it easier to collaborate on agreements.

• Allow administrator to share library documents with multiple groups – Allows school administrators to distribute document templates to different user groups, such as career advisors or administrative staff.

• Allow all users to share library documents with multiple groups – Lets any user share library documents across multiple groups, which could lead to unregulated sharing.

---

Recommended Settings:

✔ Allow creating library templates and reusable form fields – Essential for maintaining a standardized Work Experience Agreement format.
✔ Allow Users to share library documents to account – Recommended for efficiency, allowing staff to access pre-approved templates.
✔ Allow administrator to share library documents with multiple groups – Useful if agreements need to be shared with different departments.

8. Attach a PDF Copy of the Signed Document in Emails

This setting controls whether a PDF copy of the signed agreement is automatically attached to email notifications after signing. Schools can use this feature to ensure that students, parents, and employers receive a copy of the completed Work Experience Agreement for their records.

---

Settings Explained:

• All recipients – Sends a PDF copy of the signed document to everyone involved in the agreement (signers, CCs, and senders).

• Internal recipients – Sends the PDF copy only to users within the school’s Adobe Sign account (e.g., staff members).

• External recipients – Sends the PDF copy only to external users (e.g., students, parents, or employers).

• No one – Prevents Adobe Sign from attaching the signed document in emails.

• Include a link in emails to view the signed agreement – Instead of attaching a PDF, recipients receive a secure link to view or download the signed agreement.

• Include an image of the first page of the agreement in emails – Adds a preview image of the agreement’s first page in email notifications.

• Files attached to email will be named as:

  • Agreement Name – Uses the agreement’s assigned name as the file name.

  • File Name – Uses the original document file name before it was signed.

  • Hybrid – Combines both the agreement name and the original file name.

---

Recommended Settings:

✔ All recipients – Ensures students, parents, employers, and staff all receive a copy of the signed agreement.
✔ Include a link in emails to view the signed agreement – Recommended for security and easier access.

🔸 Optional:

• Include an image of the first page of the agreement in emails – Enable if signers need a quick preview.

9. File Naming for Attached Documents

This setting determines how signed agreements are named when attached to emails. Schools should configure this to ensure consistency when storing and referencing signed Work Experience Agreements.

---

Settings Explained:

• Agreement Name – Uses the title of the agreement set in Adobe Sign as the file name. This helps keep documents organized and easy to identify.

• File Name – Uses the original file name before it was uploaded to Adobe Sign. This may be useful if agreements are consistently named before sending.

• Hybrid – Combines both the Agreement Name and the original File Name, which can provide more details in the file name but may result in longer filenames.

---

Recommended Settings:

✔ Agreement Name – Ensures a clear and consistent naming structure for Work Experience Agreements.

10. Attach Audit Report to Documents

The audit report provides a detailed log of the agreement’s signing process, including timestamps, signer details, and IP addresses. This helps schools maintain a legal and verifiable record of Work Experience Agreements.

---

Settings Explained:

• Never – The audit report is not attached to the signed document email.

• For Sender Only – The audit report is only sent to the staff member who initiated the agreement.

• Always – The audit report is attached to all signed document emails, ensuring everyone receives a record.

• Attach current audit report to documents when downloaded – Ensures that the latest version of the audit report is included whenever the document is downloaded from Adobe Sign.

---

Recommended Settings:

✔ Always – Ensures that students, parents, and employers receive a copy of the audit report for transparency.

11. Merge Multiple Documents into One Document After Signing

This setting determines whether multiple documents signed within the same agreement are merged into a single PDF file or kept as separate attachments. Schools may use this to simplify document management for Work Experience Agreements that require multiple forms.

---

Settings Explained:

Keep documents separated

• If this option is unchecked, all documents in the agreement will be merged into a single PDF file for easier storage.

• If this checkbox is enabled, each document remains a separate file, maintaining its original structure.

---

Recommended Settings:

• Leave the box unchecked (Merge documents) – Recommended if schools prefer one combined file to simplify storage and reduce the number of attachments sent.

12. Download Individual Documents

This setting determines whether participants can download individual documents while they are signing or viewing an agreement. Schools may use this to allow students, parents, or employers to review documents before completing the signing process.

---

Settings Explained:

• Allow participants to download individual documents while signing or viewing

  • If this option is checked, signers can download each document separately before signing.

  • If this option is unchecked, signers can only view the document in Adobe Sign but cannot download it until after signing.

---

Recommended Settings:

• Enable this option – Recommended only if signers need to download and review documents before signing (e.g., for legal or parental review).

13. Upload Signed Document

This setting allows senders to manually upload a signed copy of the document if they receive a physical or externally signed version from a signer. Schools may use this when a student, parent, or employer signs the agreement outside of Adobe Sign and returns a scanned or hardcopy version.

---

Settings Explained:

• Allow senders to manually upload a signed copy they received from the signer

  • If checked, staff can upload a scanned or externally signed document to complete the agreement process in Adobe Sign.

  • If unchecked, agreements must be completed digitally within Adobe Sign, preventing manual uploads.

---

Recommended Settings:

• Enable this option – Recommended for schools to handle cases where a parent or employer signs a printed copy and returns it outside the digital system.

14. Delegation for Users in My Account

This setting controls whether users can delegate their signature responsibility to someone else. Schools may use this feature if administrators or staff need to sign on behalf of another person, such as when a teacher is unavailable to approve a Work Experience Agreement.

---

Settings Explained:

• Yes, can delegate to anyone – Allows users to delegate their signature to any person, including external users.

• Yes, but only to other users in my account – Limits delegation to only staff members within the school’s Adobe Sign account.

• No, delegation is not allowed – Prevents users from delegating their signature to anyone else.

---

Recommended Settings:

• Yes, but only to other users in my account – Recommended for schools to allow controlled delegation while ensuring only authorized staff members can sign on someone’s behalf.

• No, delegation is not allowed – Use this setting if the school requires strict signature accountability.

15. Allow External Recipients to Delegate Their Signature

This setting determines whether external recipients (such as students, parents, or employers) can delegate their signing responsibility to another person. Schools may need this feature if an employer contact changes or a parent authorizes another guardian to sign on their behalf.

---

Settings Explained:

• If checked, external recipients can delegate their signing responsibility to another person.

• If unchecked, only the original recipient can sign the document, and delegation is not allowed.

---

Recommended Settings:

• Enable this option – it is expected that there will be situations where external signers (parents, employers) may need to delegate signing authority.

16. Set a Default Time Zone for Agreements

This setting defines the default time zone applied to agreements created by users in the account. Setting the correct time zone ensures that timestamps on agreements, notifications, and audit reports reflect the school’s local time.

---

Settings Explained:

• Dropdown menu – Allows selection of the appropriate time zone for the school’s location.

• Use selected timezone for audit reports – If checked, ensures that audit logs also follow the selected time zone, maintaining consistency in record-keeping.

---

Recommended Settings:

• Select your local time – Schools in Australia should select this option to align timestamps with local time.

• Enable ‘Use selected timezone for audit reports’ – Ensures audit logs match the time zone of agreement activities, reducing confusion when verifying document history.

17. Set a Default Date Format for Agreements

This setting defines the default date format for agreements created in the account. Ensuring the correct format helps maintain consistency in record-keeping and compliance with local standards.

---

Settings Explained:

• Dropdown menu – Allows selection of the preferred date format.

• Use selected date format in signatures – If checked, ensures that dates in signatures follow the chosen format, preventing confusion.

---

Recommended Settings:

• Date (dd/mm/yyyy) – Recommended for Australian schools as it aligns with the standard Australian date format.

• Enable ‘Use selected date format in signatures’ – Ensures that all signatures display dates consistently, reducing misinterpretation.

18. Users in Multiple Groups

This setting determines whether users can be assigned to multiple groups within Adobe Sign. Schools may use this feature to organize staff into different roles, such as teachers, administrators, and coordinators, allowing them to access specific agreements based on their group.

---

Settings Explained:

• Disable Now – Turns off the ability for users to be in multiple groups. This is not reversible without following Adobe Sign’s prerequisite steps.

• Group assignment removes a user from the default group if it is their primary – If enabled, moving a user to another group will automatically remove them from their primary/default group.

---

Recommended Settings:

• Keep Users in Multiple Groups enabled – Recommended for schools where staff need access to agreements across different departments (e.g., career advisors and school administrators).

• Enable ‘Group assignment removes a user from the default group if it is their primary’ – This setting is highly recommended to prevent users from remaining in the default group, as this is a global group where all users can see agreements. Enabling this ensures that access is properly controlled and restricted to designated groups.
  Example: If a teacher is added to a “Work Experience Coordinators” group but remains in the default group, they will still see all agreements visible to the entire school. By enabling this setting, they will be automatically removed from the default group, ensuring they only see the agreements relevant to their assigned role.

19. Group Administrator Permissions

This setting controls what group administrators can manage within Adobe Sign. Schools can use this feature to delegate administrative responsibilities to specific staff members, such as Work Experience Coordinators, without giving them full system-wide access.

---

Settings Explained:

Group administrators can edit group settings

• Grants group admins the ability to modify settings for their assigned group without affecting other groups in Adobe Sign.

• The following options control what specific settings they can edit:

  • Group Settings – Allows admins to modify group preferences, such as default agreement settings and permissions.

  • Group Setup – Enables configuration of group-level rules, such as naming conventions and access policies.

  • Signature Preferences – Lets admins control signature formats (e.g., e-signature or digital signature requirements).

  • Digital Signatures – Manages settings for using certificate-based digital signatures for authentication.

  • Digital Identity – Configures identity verification methods for signers, such as government ID checks.

  • Security Settings – Allows admins to define password policies and authentication requirements for agreements.

  • Send Settings – Lets admins adjust options related to sending agreements, including default recipient roles.

  • Message Templates – Enables admins to create predefined email messages for agreement notifications.

  • Signer Messaging – Controls whether signers can send messages or comments while reviewing an agreement.

  • Bio-Pharma Settings – Specific to regulated industries; likely not relevant for schools.

  • Payments Integration – Allows integration with payment processors for collecting fees before an agreement is signed (not commonly used in schools).

  • External Archive – Enables automatic storage of signed agreements in external locations such as SharePoint or Google Drive.

  • Group Languages – Lets admins configure language preferences for agreement interfaces and notifications.

  • Email Settings – Allows control over email notification formats, reply-to addresses, and branding customization.

  • Group Sharing Status – Determines if group settings can be shared across multiple groups, which can impact permissions.

Group administrators can edit user profile information

• Allows group admins to update user details, such as names, email addresses, and job titles for members in their group.

Group administrators can edit user permissions

• Grants group admins the ability to assign roles and permissions to users within their group, including adjusting what features they can access.

Group administrators can add or remove users from a group

• Controls how group admins manage users within their assigned groups. Options include:

  • Adding new users to the account or assigning existing account users to a group – Allows group admins to create new users and add them to a group or move existing users into specific groups.

  • Group admins can remove users from the account’s default group – If checked, admins can remove users from the default group, ensuring that access is controlled appropriately.

---

Recommended Settings:

• ✔ Enable all options under ‘Group administrators can edit group settings’ – Schools should enable all to allow admins full control over their group’s settings except for ‘Bio-Pharma Settings’ and ‘Payments Integration’, which are not applicable to schools.

• ✔ Enable ‘Group administrators can edit user permissions’ – This should be enabled if admins need to adjust access levels within their group, ensuring staff have the right permissions.

• ✔ Enable ‘Group admins can remove users from the account’s default group’ – This prevents users from remaining in the global default group, where they would have unnecessary access to agreements.

• ❌ Disable ‘Group administrators can edit user profile information’ – It is recommended to leave this unchecked so that IT administrators centrally manage user profiles to avoid unauthorized changes.

20. Replace Recipient

This setting controls how recipient replacement is handled when a signer needs to be changed. Schools may use this feature if a student, parent, or employer changes and a new recipient needs to sign the Work Experience Agreement instead.

---

Settings Explained:

• Only the new recipient will be able to participate – When a recipient is replaced, only the new person can sign or interact with the agreement. The original recipient loses access.

• The original recipient and the new recipient will both be able to participate – Allows both the original and new recipients to sign or take action on the agreement.

• Users in my account can select whether the original recipient can or cannot participate after being replaced – If enabled, users in the account can decide per agreement whether the original recipient remains involved after being replaced.

---

Recommended Settings:

• The original recipient and the new recipient will both be able to participate – Recommended as this ensures continuity in the signing process if the original recipient still needs to be involved in the agreement.

21. Audit Report

The audit report logs all actions taken on an agreement, such as when it was sent, viewed, signed, or modified. Schools can use this to track document activity for compliance and record-keeping, ensuring transparency in Work Experience Agreements.

---

Settings Explained:

• Allow unauthenticated access to audit report on transaction verification page – If enabled, anyone with the audit report link can view it without authentication, which may reduce security.

• Include reminders in audit report – Adds a record of any reminder emails sent for unsigned agreements.

• Include agreement view events in audit report – Logs when recipients open/view the agreement, providing additional tracking.

• Include agreement page count and attachment count in audit report for completed agreements – Displays the total number of pages and attachments in the final audit report.

• Include document names in audit report for completed agreement – Shows the file names of the signed documents in the audit report.

• Include document names within each audit event – Adds document names to each entry in the audit log, making it easier to identify changes.

• Mask phone numbers in audit report – Hides phone numbers in the report to protect recipient privacy.

---

Recommended Settings:

• Mask phone numbers in audit report – Recommended to protect recipient privacy, ensuring sensitive data isn’t exposed.

• Include agreement view events in audit report – Helps track when agreements were accessed, providing visibility into signer activity.

• Include document names in audit report for completed agreement – Recommended if schools need to quickly reference signed documents in audit records.

22. New Request Signature Experience

This setting determines whether users can access the new version of the Request Signature interface in Adobe Sign. The new experience improves the signing workflow with a modernized UI and additional features. Schools can use this to streamline Work Experience Agreement requests for staff, students, and parents.

---

Settings Explained:

• Users can toggle between the new and classic Request Signature experience – Allows users to switch between the new and old interface, providing flexibility.

• Set the new Request Signature as the default experience – Automatically enables the new interface for all users unless they manually switch back to the classic version.

---

Recommended Settings:

• ✔ Enable ‘Users can toggle between the new and classic Request Signature experience’ – Allows users to choose the interface that works best for them, ensuring a smoother transition to the new experience.

• ✔ Enable ‘Set the new Request Signature as the default experience’ – Ensures all users benefit from the updated workflow and improved usability while still having the option to revert if needed.

23. Click on Save

Once all settings have been configured, clicking the Save button ensures that the changes are applied and stored in the Adobe Sign system.

Account Setup

The Account Setup section in Adobe Sign contains foundational settings that define how the system is configured for a school. These settings control branding, user management, default agreement behaviors, and integration options. Proper configuration ensures that the platform aligns with the school’s workflow, security, and compliance requirements for Work Experience Agreements.

24. Select Account Setup

25. Upload a Logo

This setting allows schools to customize Adobe Sign with their branding by adding a school logo. The logo will appear in the application header and email notifications, providing a more professional and recognizable experience for students, parents, and employers.

---

Steps to Upload a Logo:

1. Click ‘Upload Logo’

   • Press the Upload Logo button to open the file selection window.

2. Select an Image File

   • Choose a JPG, GIF, or PNG file from your computer.

   • Recommended dimensions and size will be provided on the screen.

3. Confirm Upload

   • After selecting the file, Adobe Sign will display a preview.

---

Recommended Settings:

• Use a high-resolution logo that is clear and easily recognizable.

• Ensure the file format is JPG, GIF, or PNG for compatibility.

• Test the branding in an email notification to ensure it displays correctly.

⚠️ Note: If you have any issues getting your image to appear correctly, ensure that the image you’re using is exactly 60 pixels tall, and up to 200 pixels wide.

26. Untitled step

This setting allows organizations to personalize the URL that users and recipients see when accessing Acrobat Sign for e-signature workflows. A custom hostname enhances brand identity and helps users recognize official communication from the organization.

---

Settings Explained:

• Hostname / URL address – Defines the custom subdomain for your Acrobat Sign account, replacing the default URL with a more recognizable company-branded URL (e.g., schoolname.au1.documents.adobe.com).

• This URL will appear in all agreement links sent to recipients for signing.

---

Recommended Settings:

• Set a custom company URL if available – Helps establish trust and ensures recipients recognize the agreement as coming from an official source.

• Use a clear and recognizable hostname – Ideally, the organization or school name should be used to maintain branding consistency.

27. Add Company Name

This setting allows schools to set a default institution name in Adobe Sign. The company name appears in agreements, email notifications, and system messages, ensuring consistency across all Work Experience Agreements.

---

Settings Explained:

• Company Name – Defines the name that will be displayed across Adobe Sign agreements and communications.

• Set company name for all users in account – If enabled, this applies the company name to all users within the Adobe Sign account.

---

Recommended Settings:

• Enter the official school name to ensure all agreements reflect the institution’s identity.

• ✔ Enable ‘Set company name for all users in account’ to maintain consistency across all users.

28. Save

Once all settings have been configured, clicking the Save button ensures that the changes are applied and stored in the Adobe Sign system.

Signature Preferences

The Signature Preferences section in Adobe Sign controls how signatures are captured, displayed, and validated for agreements. These settings ensure that schools can define consistent, legally compliant, and secure signature workflows for Work Experience Agreements.

29. Click on Signature Preferences

30. Signature Formatting Options

This setting controls how signatures and initials appear on agreements. Enabling these options ensures that signatures are visually clear, properly aligned, and professionally formatted, which is useful for Work Experience Agreements.

---

Settings Explained:

• Use well-formatted signatures and initials – Ensures that typed and drawn signatures are displayed in a consistent and professional manner.

• Dynamically adjust line below the signature and initials – Adjusts the signature line based on the size and style of the signature, improving readability.

---

Recommended Settings:

• ✔ Enable ‘Use well-formatted signatures and initials’ – This ensures that all signatures, whether typed or drawn, appear uniform and professional, making agreements look consistent across different signers. This is particularly useful for Work Experience Agreements that require formal documentation.

• ✔ Enable ‘Dynamically adjust line below the signature and initials’ – This allows the signature line to adjust based on the signer’s input, ensuring that signatures do not overlap or appear misaligned. This is useful when different signers have varying signature sizes, improving document readability.

31. Allow Recipients to Sign and Initial By

This setting determines the methods recipients can use to sign and initial agreements. Schools can use this to provide flexibility for students, parents, and employers when signing Work Experience Agreements while maintaining security and compliance.

---

Settings Explained:

• Typing their name and initials – Allows signers to type their signature instead of drawing it.

  • Dynamically choose signing font – If enabled, Adobe Sign automatically assigns a randomized font style to typed signatures.

• Drawing a handwritten signature and initials – Allows signers to draw their signature using a mouse, touchscreen, or stylus.

• Uploading an image of their signature and initials – Enables signers to upload a scanned image of their handwritten signature for consistency.

• Signers can change their name or initials – Allows signers to modify their displayed name before signing, which can be useful if a user’s name appears incorrectly.

• Witness can change their name or initials – Allows a witness to edit their name or initials before signing, ensuring accuracy in the document.

---

Recommended Settings:

• ✔ Enable ‘Typing their name and initials’ – Allows signers to quickly enter a digital signature, ensuring accessibility for all recipients.

• ✔ Enable ‘Drawing a handwritten signature and initials’ – Provides a more personal and legally recognizable signature method.

• ✔ Enable ‘Uploading an image of their signature and initials’ – Allows recipients to use a consistent signature if required by school policy.

• ✔ Enable ‘Signers can change their name or initials’ – Ensures that users can correct any errors in their name display before signing.

32. Allow Recipients to Use Their Saved Signature

This setting controls whether recipients can reuse a previously saved signature for signing agreements. Schools can use this to speed up the signing process for frequent users while ensuring compliance and security.

---

Settings Explained:

• All recipients – Allows both internal (staff) and external users (students, parents, employers) to use their saved signature.

• Internal recipients – Limits saved signatures to only users within the school’s Adobe Sign account (e.g., staff members).

• No one – Disables the ability to reuse saved signatures, requiring signers to enter a new signature each time.

• Allow users in my account to upload an image and save to their profile as their signature – Allows internal users to upload and store an image of their signature for future use.

---

Recommended Settings:

• ✔ Enable ‘All recipients’ – Allows signers to reuse their saved signature, making the signing process faster and more convenient, especially for frequent agreements like Work Experience forms.

• ✔ Enable ‘Allow users in my account to upload an image and save to their profile as their signature’ – This lets staff members store their handwritten signature image, ensuring a consistent and professional appearance in documents.

33. Navigate Recipients Through Form Fields When Filling and Signing Agreements

This setting determines whether signers are automatically guided through required fields when filling and signing agreements. Enabling this ensures that recipients don’t miss mandatory fields, making the signing process smoother and reducing errors.

---

Settings Explained:

• All recipients – Enables guided navigation for both internal (staff) and external (students, parents, employers) users when completing agreements.

• Internal recipients – Limits guided navigation to only users within the school’s Adobe Sign account (e.g., staff members).

• External recipients – Enables navigation only for external users, such as students or parents.

• No one – Disables guided navigation, requiring signers to manually locate and complete fields.

---

Recommended Settings:

• ✔ Enable ‘All recipients’ – Ensures that all users are guided through required fields, reducing the chance of missed information and improving completion rates for Work Experience Agreements.

34. Restart Agreement Workflow

This setting determines whether recipients can restart an agreement workflow, sending it back to the first participant. This can be useful when errors are found in the document or when information needs to be re-entered before finalization.

---

Settings Explained:

• Allow recipients to restart the agreement workflow and send it back to the first participant – If enabled, signers can restart the workflow, requiring all previous steps to be repeated.

---

Recommended Settings:

• ✔ Highly recommended to enable ‘Allow recipients to restart the agreement workflow’ – This feature is useful in school workflows where errors need to be corrected without canceling the entire agreement.

  Example: A principal reviews a Work Experience Agreement and notices that a student entered the wrong employer details. Instead of canceling the agreement and creating a new one, the principal can restart the workflow and add a message, allowing the student to correct the error while keeping the original agreement intact. This saves time and maintains a clear audit trail of the correction.

35. Decline to Sign

This setting allows signers to decline signing an agreement if they believe it contains incorrect information or is not appropriate for them to sign. This feature is useful for schools as it ensures that agreements are properly reviewed and errors can be flagged before finalization.

---

Settings Explained:

• Allow signers to decline – Gives signers the ability to refuse signing an agreement if they have a valid reason.

• Acceptors: Enable ‘Decline’ button and always display legal footer for the agreement – If enabled, this adds a decline button to agreements and ensures that a legal footer is displayed.

• Require signers to provide a reason when declining to sign – Ensures that signers must state a reason before rejecting an agreement.

• Allow signers to provide their custom reason to decline signing – Allows signers to enter their own explanation instead of choosing from predefined reasons.

• Create and manage decline to sign reasons – Schools can define preset decline reasons for consistency in responses.

---

Recommended Settings:

• ✔ Enable ‘Allow signers to decline’ – Ensures that students, parents, and employers can refuse to sign if the information is incorrect or requires changes.

• ✔ Enable ‘Require signers to provide a reason when declining to sign’ – Ensures that every declined agreement has a justification, making it easier to review and correct issues.

• ✔ Enable ‘Allow signers to provide their custom reason to decline signing’ – Gives signers the flexibility to describe their concerns clearly, rather than selecting from a predefined list.

36. Additional Settings

These settings provide extra customization options for how agreements are signed and processed. Schools can enable features that improve document tracking, user experience, and security while ensuring compliance with Work Experience Agreement workflows.

---

Settings Explained:

• Allow Stamps Workflows – Enables signers to use a stamp (such as a school or employer seal) in place of a signature.

  • Allow signers to sign with Stamp alone – Lets users sign only with a stamp without needing a handwritten or typed signature.

• Require signers to provide their job title when e-signing – Forces signers to enter their job title, which can be useful for employer representatives.

• Require signers to provide their company name when e-signing – Ensures that organizations/employers signing agreements include their company name, which can help identify signatories in reports.

• Allow signers to print, place written signatures, and upload the agreement back to Adobe Sign – Lets signers print the document, sign it manually, and re-upload it instead of e-signing.

• Show message to recipients when e-signing – Displays a custom message to signers, which can be useful for providing instructions or reminders during signing.

• Require signers to use a mobile device to create their signature and initials – Forces signers to only sign on a mobile touchscreen device, restricting other signing methods.

• Request IP address from signers – Logs the IP address of signers to provide additional tracking and verification.

• Exclude company name and job title in the participation stamp – Removes these details from the participation stamp that appears in the signed agreement.

• Apply Adaptive Signature Draw Scaling – Adjusts the size of drawn signatures to fit neatly in signature fields.

---

Recommended Settings:

• ✔ Enable ‘Allow signers to print, place written signatures, and upload the agreement back to Adobe Sign’ – Provides flexibility in cases where e-signature is not an option, such as when an employer requires a wet signature.

• ✔ Enable ‘Show message to recipients when e-signing’ – Allows schools to provide instructions or reminders about completing the Work Experience Agreement correctly.

• ✔ Enable ‘Apply Adaptive Signature Draw Scaling’ – Ensures that drawn signatures fit properly, improving document readability.

37. Click on Save

Once all settings have been configured, clicking the Save button ensures that the changes are applied and stored in the Adobe Sign system.

Security Settings

The Security Settings section in Adobe Sign allows schools to configure authentication, access control, and data protection measures to ensure that Work Experience Agreements are handled securely. These settings help protect sensitive student and employer information while ensuring compliance with school policies.

38. Click on Security Settings

39. PDF Encryption Type

This setting controls the level of encryption applied to signed agreements, ensuring that PDF documents are protected against unauthorized access or tampering. Higher encryption levels provide stronger security, but may limit compatibility with older software.

---

Settings Explained:

• 128-bit AES (Compatible with Acrobat 7.0 and later) – Uses Advanced Encryption Standard (AES) with a 128-bit key, offering moderate security while maintaining compatibility with older versions of Adobe Acrobat.

• 256-bit AES (Compatible with Acrobat X and later) – Provides stronger encryption with a 256-bit key, making the document more secure but requiring a newer version of Adobe Acrobat to open.

---

Recommended Settings:

• ✔ Enable ‘256-bit AES’ – Highly recommended for maximum security, ensuring that signed agreements are protected from unauthorized access and tampering.

⛔️ Critical: This setting is required during the deployment process to enable DynAPPix to upload templates successfully.✔ Enable ‘Allow group administrators to develop applications that use the API’ – Ensures group admins can generate API keys, allowing controlled API access for Power Automate workflows and template management, while reducing reliance on full account administrators.

40. API

This setting controls API access permissions for integrating Adobe Sign with external applications, such as Power Automate or custom-built solutions using an API integration key. Proper configuration is critical for schools that want to automate document workflows or connect Adobe Sign with other systems.

---

Settings Explained:

• Allow Uncertified partner applications to access data – Enables third-party applications that aren’t officially certified by Adobe to interact with Adobe Sign.

• Allow all users who aren’t account administrators to develop applications – Grants non-administrators the ability to create and use API-based applications, such as Power Automate integrations.

• Allow group administrators to develop applications that use the API – Allows group administrators (not just full account admins) to generate API keys and manage integrations.

---

Critical Setting:

• ✔ Enable ‘Allow group administrators to develop applications that use the API’ – Ensures that group admins can generate API keys, reducing dependency on full account administrators while maintaining security.

41. Manage Account Sharing

This setting controls how Adobe Sign accounts are shared between users. Account sharing can allow multiple users to access agreements, send documents on behalf of others, or manage workflows collaboratively. For schools, restricting account sharing helps maintain security and compliance when handling Work Experience Agreements.

---

Settings Explained:

• Account administrators manage sharing – Only administrators can control which users share accounts or request access to others.

• Do not allow account sharing – Completely disables account sharing, ensuring each user works independently.

• Allow users to request access to other user accounts – Enables users to request permission to manage agreements on behalf of others.

• Allow users to share their account with others – Lets users give access to their account, allowing another person to send and manage agreements for them.

• Allow users to both request access to other accounts and to share their account – Fully enables account sharing, allowing users to request access to others’ accounts and share their own.

---

Recommended Settings:

• ✔ Enable ‘Allow users to share their account with others’ – Required for Adobe’s advanced sharing protocol, allowing the service account to share agreement modification access with the Work Experience Careers group.

• ✔ Enable ‘Account administrators manage sharing’ – Ensures only administrators control account access, preventing unauthorized sharing.

⛔️ Critical: Adobe’s advanced sharing protocol will be used to allow a service account to create agreements via Power Automate and share modification access with users in the Work Experience Careers group.✔ Enable ‘With internal accounts’ – Required to allow agreement sharing within the organization, ensuring that the service account can distribute agreements to the correct users.✔ Enable ‘Sending’ – Ensures that shared users can send agreements on behalf of the service account, streamlining the workflow.✔ Enable ‘Modify existing transactions’ – Essential for allowing shared users to edit agreements created by the service account, ensuring they can make necessary changes without creating a new agreement.

⚠️ Account Sharing Permissions will not be available until Advanced Sharing is turned on

42. Account Sharing Permissions

This setting controls whether agreements can be shared across accounts and what level of access users have to send or modify agreements created by another user. For this setup, Adobe’s advanced sharing protocol is being used to allow a service account to create agreements via Power Automate and grant modify access to the Work Experience Careers group.

---

Settings Explained:

• With external accounts – Allows agreements to be shared with users outside the organization.

• With internal accounts – Allows agreements to be shared with users within the same organization.

  • Sending – Allows shared users to send agreements on behalf of the account owner.

  • Modify existing transactions – Allows shared users to edit agreements created by the account owner.

---

Required Settings:

🔴 Critical: These settings are required for the service account to correctly share agreements with the Work Experience Careers group.

• ✔ Enable ‘With internal accounts’ – Required to allow agreement sharing within the organization, ensuring that the service account can distribute agreements to the correct users.

• ✔ Enable ‘Modify existing transactions’ – Essential for allowing shared users to edit agreements created by the service account, ensuring they can make necessary changes without creating a new agreement.

• ❌ Disable ‘With external accounts’ – External sharing is not required and should be disabled to maintain security.

43. Agreement Sharing Controls

This setting determines whether users can share agreements with others inside or outside the organization. For schools, restricting sharing to internal users ensures that Work Experience Agreements remain secure and are only accessible by authorized staff.

---

Settings Explained:

• Internal User – Allows agreements to be shared within the same organization.

• External User – Allows agreements to be shared with users outside the organization, such as external partners or vendors.

---

Recommended Settings:

🔴 Critical: These settings are required to support agreement sharing within the Work Experience Careers group while maintaining security.

• ✔ Enable ‘Internal User’ – Ensures agreements can be shared within the organization, allowing designated staff to access and manage Work Experience Agreements.

• ❌ Disable ‘External User’ – Prevents sharing agreements with unauthorized external parties, reducing data security risks.

44. Document Password Strength

This setting enforces a password policy for agreement signing, PDF encryption, and access control. Schools handling sensitive Work Experience Agreements should require strong passwords to protect documents from unauthorized access.

---

Settings Explained:

• None – Any password is allowed – No restrictions on password strength, making documents more vulnerable.

• Standard – At least 6 characters – Minimum password requirement, but relatively weak security.

• Medium – At least 7 characters, must include uppercase or a number – Adds a basic level of security.

• Strong – At least 8 characters, must include lowercase, uppercase, and numbers – Ensures stronger protection against unauthorized access.

• Stronger – At least 14 characters, must include lowercase, uppercase, and numbers – Maximum security, but may be difficult for users to manage.

---

Recommended Settings:

🔴 Highly Recommended: Schools must enforce a secure password policy to protect sensitive agreements.

• ❌ Avoid ‘None’ or ‘Standard’ – These options do not provide sufficient security for Work Experience Agreements.

• ✔ Enable ‘Strong’ (8+ characters, mix of cases & numbers) – Recommended to balance security and usability while ensuring agreements are well protected.

• ✔ Enable ‘Stronger’ (14+ characters) if handling highly confidential agreements – Provides maximum protection but may be impractical for daily use.

45. Block signers from signing within a particular geography

This setting restricts where signers can complete agreements based on their geographic location. Schools may consider using this setting only if there is a need to prevent document signing outside of authorized regions.

---

Settings Explained:

• Block by location – When enabled, this setting prevents signers in specific geographic regions from completing agreements.

---

Recommended Settings:

🔴 Not Recommended for most school environments unless there is a specific legal or compliance requirement.

• ❌ Disable ‘Block by location’ – Allow signers to complete agreements from any location to ensure flexibility for students, parents, and employers who may be traveling or signing remotely.

46. Click on Save

Once all settings have been configured, clicking the Save button ensures that the changes are applied and stored in the Adobe Sign system.

Send Settings

The Send Settings section controls how agreements are sent, managed, and processed within Adobe Sign. These settings determine who can send agreements, how agreements are tracked, and what security measures apply when sending documents.

For schools using Work Experience Agreements, these settings should ensure streamlined sending processes while maintaining security and compliance.

47. Click on Send Settings

48. Require Recipient Name When Sending from Adobe Acrobat Sign Web Application

This setting controls whether a recipient’s name must be entered when sending agreements from the Adobe Acrobat Sign web application. For schools handling Work Experience Agreements, ensuring recipient names are included helps maintain clarity and accuracy in tracking agreements.

---

Settings Explained:

• Allow recipient name to be entered on Send – Enables senders to manually enter recipient names before sending an agreement.

• Make this field mandatory – Requires that a recipient’s name be entered before an agreement can be sent.

---

Recommended Settings:

✔ Enable ‘Allow recipient name to be entered on Send’ – Ensures that senders can enter recipient names, helping to keep agreements organized.

49. Allowed Recipient Roles

This setting defines the roles recipients can take when signing or reviewing an agreement. Schools using Adobe Sign for Work Experience Agreements may require various roles depending on approval processes involving students, parents, and employers.

---

Settings Explained:

• Approvers – Recipients who review and approve the agreement but do not sign it.

• Delegators – Recipients who assign the agreement to another person for approval or signing.

• Acceptors – Recipients who acknowledge the agreement but do not provide an official approval or signature.

• Certified Recipients – Recipients who receive the agreement for verification purposes, ensuring compliance.

• Form Fillers – Recipients who fill out required fields in an agreement but are not signers.

• Electronic Sealers – Users who apply a digital seal or electronic stamp to the agreement.

• Signers with Witness – Recipients who must have their signature witnessed by another party.

---

Recommended Settings:

✔ Enable ‘Approvers’ – Allows principals or career advisors to approve agreements before they are finalized.

✔ Enable ‘Delegators’ – Useful when recipients need to forward the agreement to another authorized individual.

✔ Enable ‘Acceptors’ – Ensures that employers or parents can confirm receipt of the agreement without signing.

✔ Enable ‘Form Fillers’ – Essential for allowing students, parents, or employers to enter required details before signing.

50. Attaching Documents

This setting controls where senders can upload documents from when creating an agreement. Schools using Adobe Sign for Work Experience Agreements should ensure reliable and secure document sources while preventing unnecessary access to external storage services.

---

Settings Explained:

• Allow senders to attach documents from their computers – Enables direct file uploads from a local device. Essential for staff who manage Work Experience Agreements.

• Allow senders to attach documents from their document library – Allows users to access pre-saved templates or reusable documents in the Adobe Sign document library.

  • Include documents from the Acrobat Sign shared library – Expands access to shared resources within the school’s account, ensuring consistency in agreements.

• Allow senders to attach documents from OneDrive – Enables document selection from Microsoft OneDrive, which is commonly used by schools and staff.

• Allow senders to attach documents from Google Drive, Dropbox, and Box.com – Provides access to external cloud storage services but may introduce security and data compliance concerns.

---

Recommended Settings:

✔ Enable ‘Allow senders to attach documents from their computers’ – Essential for allowing staff to upload agreements directly from their device.

✔ Enable ‘Allow senders to attach documents from their document library’ – Ensures access to pre-approved templates, improving efficiency.

✔ Enable ‘Include documents from the Acrobat Sign shared library’ – Allows schools to use centrally managed documents for consistency.

✔ Enable ‘Allow senders to attach documents from OneDrive’ – Recommended if schools store agreements in Microsoft 365.

❌ Disable Google Drive, Dropbox, and Box.com integration – Helps maintain data security and compliance by restricting document uploads to approved storage locations.

51. Modify Agreements

This setting allows senders to make changes to an agreement after it has been sent but before it is completed. For schools managing Work Experience Agreements, enabling this feature ensures that errors or missing information can be corrected without restarting the process.

---

Settings Explained:

• Allow senders to modify agreements – Grants users the ability to edit agreements before they are fully executed. This includes correcting errors, updating details, or adding missing information.

---

Recommended Settings:

✔ Enable ‘Allow senders to modify agreements’ – Highly recommended for schools, as it allows staff to fix mistakes or update agreements without canceling and restarting the process.

52. Agreement Name

This setting allows senders to rename agreements before sending them for signature. For schools using Adobe Sign for Work Experience Agreements, enabling this feature ensures that agreements are clearly labeled and easy to identify in records and reports.

---

Settings Explained:

• Allow sender to edit agreement name – Grants users the ability to customize the name of agreements before sending. This can help distinguish between multiple agreements and improve record-keeping clarity.

---

Recommended Settings:

✔ Enable ‘Allow sender to edit agreement name’ – Recommended to allow schools to assign meaningful names to agreements, making it easier to track specific student placements or employer agreements.

53. Private Messages to Recipients

This setting allows senders to include a private message for each recipient in an agreement. In a school setting, this can be useful for providing custom instructions, clarifications, or reminders specific to each recipient, such as students, parents, and employers.

---

Settings Explained:

• Allow senders to include a private message to each of the recipients – Enables senders to add personalized messages that only the specified recipient can see. This can be useful for guidance on next steps, addressing recipient-specific concerns, or adding confidential notes.

---

Recommended Settings:

✔ Enable ‘Allow senders to include a private message to each of the recipients’ – Highly recommended for Work Experience Agreements, as it allows schools to provide role-specific instructions (e.g., different guidance for students, parents, and employers).
Note: this will only effect Agreements sent manually and not via the WorkEx system

54. Allowed Signature Types

This setting determines which signature methods are permitted when sending agreements. Schools using Adobe Sign for Work Experience Agreements may require electronic signatures for faster processing, but written signatures may still be needed for specific scenarios where manual signing is preferred.

---

Settings Explained:

• Allow senders to send documents for Electronic signature – Enables documents to be signed digitally, providing a faster, legally binding, and paperless solution.

• Allow senders to send documents for Written signature – Allows senders to request a printed document for manual signing, which can then be uploaded back into Adobe Sign.

• Default Signature Type – Determines whether Electronic or Written signatures are selected by default when sending agreements.

---

Recommended Settings:

✔ Enable ‘Allow senders to send documents for Electronic signature’ – Highly recommended as the default option for faster, more efficient processing.
✔ Enable ‘Allow senders to send documents for Written signature’ – Recommended for cases where a manual signature is legally required or preferred by certain recipients.
✔ Set ‘Electronic’ as the default signature type – Ensures that digital signing is prioritized, reducing processing delays and administrative overhead.

55. Reminders

This setting allows senders to configure automated reminders for recipients who have not yet signed or completed their agreements. Reminders help ensure that work experience agreements are signed on time, reducing the need for manual follow-ups.

---

Settings Explained:

• Allow senders to set reminders on the send page – Lets senders configure custom reminders when sending an agreement. This flexibility is useful for urgent agreements that need a faster turnaround.

• Set a default reminder for agreements created by users in this account – Automatically applies a predefined reminder schedule to all agreements, ensuring consistent follow-ups without manual intervention.

---

Recommended Settings:

✔ Allow senders to set reminders on the send page – Allows flexibility for senders to decide when and how often reminders should be sent.

56. Document Expiration

This setting controls whether agreements expire after a set period, ensuring timely completion and preventing outdated agreements from being signed. Expiration deadlines help maintain compliance with school policies and Work Experience Agreement timelines.

---

Settings Explained:

• Enable document expiration – Activates expiration settings for agreements, preventing signers from completing the document after a specified timeframe.

• Allow senders to set or modify expiration settings per document – Gives senders the ability to define expiration dates for each agreement individually.

• Allow modification of expiration settings after the document is sent – Allows senders to extend or adjust expiration dates even after the agreement has been sent.

• Limit number of days signers will have to sign documents – Enforces a fixed signing period by specifying the number of days before expiration.

• Include internal signers when applying document expiration deadlines – Ensures that both internal and external recipients adhere to the expiration policy.

• Include expiration information in emails sent to signers – Notifies recipients of the deadline in their email notifications, reducing the risk of missed signing deadlines.

---

Recommended Settings:

✔ Enable document expiration – Ensures agreements do not remain open indefinitely, keeping document processing on track.
✔ Allow senders to set or modify expiration settings per document – Provides flexibility for senders to determine deadlines based on urgency.
✔ Include internal signers when applying document expiration deadlines – Ensures consistency in expiration enforcement for both internal and external signers.
✔ Include expiration information in emails sent to signers – Keeps signers informed of deadlines to reduce missed completions.

⛔ Disable ‘Allow modification of expiration settings after the document is sent’ – Prevents unauthorized extensions, ensuring deadlines are enforced.
⛔ Disable ‘Limit number of days signers will have to sign documents’ – Instead, allow senders to configure expiration per document for flexibility.

57. Preview, position signatures or add form fields

This setting controls how senders interact with documents before sending them for signing. It allows users to preview agreements, adjust signature placements, and add form fields to ensure a smooth signing experience.

---

Settings Explained:

• Make document preview and authoring selected by default – Automatically enables document preview and editing when sending an agreement, allowing senders to position signatures and form fields before finalizing.

• Allow senders to modify document preview settings per document – Gives senders the flexibility to enable or disable document preview and editing for each agreement as needed.

• Allow Acrobat Sign to suggest possible form fields within the document – Uses AI-based detection to recommend form fields, making it easier to structure agreements with required input areas.

---

Highly Recommended Settings:

• ✔ Enable ‘Make document preview and authoring selected by default’ – Ensures that all agreements are reviewed and properly formatted before being sent, reducing errors and misplaced signatures.

• ✔ Enable ‘Allow senders to modify document preview settings per document’ – Provides flexibility for senders to adjust preview settings based on the complexity of the agreement.

• ✔ Enable ‘Allow Acrobat Sign to suggest possible form fields within the document’ – Automates form field detection, improving efficiency when preparing agreements for signing.

58. Signing Order

This setting determines the sequence in which recipients sign an agreement. It provides flexibility for organizations to enforce a strict signing order or allow recipients to sign in any order.

---

Settings Explained:

• Recipients will sign in the order they are entered – Signers are required to sign in a predefined sequence, ensuring structured approval processes.

• Recipients will sign in any order – Allows recipients to sign in any sequence, removing restrictions on signing order.

• Allow senders to select signing order – Gives senders the ability to choose between sequential or unordered signing on a per-agreement basis.

• Allow senders to specify hybrid routing order – Enables a mix of sequential and parallel signing, where some recipients must sign in order while others can sign at any time.

---

Recommended Settings:

• ✔ Enable ‘Recipients will sign in the order they are entered’ – Ensures that approvals follow a structured process, which is important for documents requiring multiple levels of authorization (e.g., Work Experience Agreements signed first by students, then parents, and finally employers).

• ✔ Enable ‘Allow senders to select signing order’ – Provides flexibility for senders to determine the best signing sequence for each agreement.

• ✔ Enable ‘Allow senders to specify hybrid routing order’ – Useful for agreements that involve both mandatory sequential signers (e.g., school staff approvals) and signers who can sign at any time (e.g., parents or students).

59. Add Myself

This setting allows senders to easily add themselves as a signer when requesting signatures. It acts as a shortcut, reducing the need to manually enter their information.

---

Settings Explained:

• Show the ‘Add Myself’ option – When enabled, senders can quickly include themselves as a recipient in the signing workflow without having to manually input their details.

---

Recommended Settings:

• ✔ Enable ‘Show the ‘Add Myself’ option’ – Useful for scenarios where the sender also needs to sign, such as school staff members approving Work Experience Agreements before sending them to students or parents. It improves efficiency by reducing manual data entry.

60. Liquid Mode

Liquid Mode enables recipients to review and sign agreements using a mobile-responsive interface. This improves readability and navigation on mobile devices, ensuring that documents are easily accessible without requiring manual zooming or scrolling.

---

Settings Explained:

• Allow recipients to review and sign in a mobile responsive view of the agreement – When enabled, agreements are dynamically reformatted for an optimized mobile signing experience, making it easier for recipients to interact with documents on smartphones and tablets.

---

Recommended Settings:

• ✔ Enable ‘Allow recipients to review and sign in a mobile responsive view of the agreement’ – This setting is recommended to enhance accessibility for parents, students, and employers who may need to sign documents on mobile devices. It ensures that agreements remain clear and easy to navigate, reducing the risk of errors or missed fields.

⚠️ These settings should match those configured under ‘Attaching Documents’ (Step 50) to maintain consistency in how users are allowed to upload files across different stages of the signing process.

61. Upload Options on E-sign Page

This setting determines how signers and approvers can upload files while completing an agreement. It ensures that users have access to the necessary document sources for smooth submission.

---

Settings Explained:

• Allow signers/approvers to upload files on e-sign page from local system – Enables users to upload files directly from their device.

• Allow signers/approvers to upload files on e-sign page from Google Drive – Allows users to attach files stored in Google Drive.

• Allow signers/approvers to upload files on e-sign page from Dropbox – Enables document selection from Dropbox.

• Allow signers/approvers to upload files on e-sign page from Box.com – Provides access to Box.com for file uploads.

• Allow signers/approvers to upload files on e-sign page from OneDrive – Enables users to attach files from their OneDrive account.

---

Recommended Settings:

• ✔ Enable ‘Allow signers/approvers to upload files on e-sign page from local system’ – Ensures that users can easily attach necessary documents from their devices.

• ✔ Enable ‘Allow signers/approvers to upload files on e-sign page from OneDrive’ – Recommended for users who store documents in OneDrive, ensuring consistency with cloud storage preferences.

62. Save

Once all settings have been configured, clicking the Save button ensures that the changes are applied and stored in the Adobe Sign system.

Email Settings

The Email Settings section controls how email notifications are sent and received for agreements within Adobe Acrobat Sign. These settings help manage communication between senders and recipients, ensuring timely updates on document status while maintaining security and compliance.

63. Click on Email Settings

64. Footer Settings

This section allows administrators to define email settings for Acrobat Sign notifications and communications. It ensures consistency in outgoing emails and controls whether individual users can modify their email footers.

Settings Explained:

• Email Footer – Administrators can define a custom footer that appears at the bottom of every email sent from Acrobat Sign.

• Allow users to have their own email footers – If enabled, users can override the default footer with their own custom content.

Recommended Settings:

• Define a standardized email footer – Ensures consistent branding and compliance with organizational communication policies.

• Disable ‘Allow users to have their own email footers’ – Prevents inconsistencies in email communication and enforces a uniform footer across all users.

65. Header Logo

This setting allows administrators to upload a custom header logo that appears in Acrobat Sign emails and web pages, ensuring consistent branding across all communications.

Settings Explained:

• Header Logo Upload – Allows administrators to upload an image file that will appear as the organization’s logo in Acrobat Sign headers. The file must not exceed 600 pixels wide and 200 pixels high.

• Clear Logo – Removes the currently uploaded logo, reverting to the default Acrobat Sign branding.

---

Steps to Upload a Header Logo:

1. Click the “Browse” Button – Opens a file selection window to choose an image file.

2. Select an Image File – Ensure the file meets the size requirement (maximum 600 pixels wide and 200 pixels high).

3. Click “Open” – The selected image will be uploaded as the header logo.

4. Verify the Logo Display – Confirm that the uploaded logo appears correctly.

---

Recommended Settings:

• Upload the organization’s logo – Ensures brand consistency across all Acrobat Sign emails and user interfaces.

66. Email Footer

This setting allows administrators to upload a custom email footer logo that appears at the bottom of all Acrobat Sign emails. This helps maintain consistent branding and professionalism across all communications.

---

Settings Explained:

• Email Footer Upload – Allows administrators to upload an image file as the footer in Acrobat Sign emails. The file must not exceed 600 pixels wide and 200 pixels high.

• Clear Logo – Removes the currently uploaded logo, reverting to the default Acrobat Sign branding.

---

Steps to Upload an Email Footer Logo:

1. Click the “Browse” Button – Opens a file selection window to choose an image file.

2. Select an Image File – Ensure the file meets the size requirement (maximum 600 pixels wide and 200 pixels high).

3. Click “Open” – The selected image will be uploaded as the email footer.

4. Verify the Footer Display – Confirm that the uploaded footer appears correctly.

---

Recommended Settings:

• Upload a custom footer logo – Ensures all Acrobat Sign emails maintain a professional and branded appearance.

67. Customize the “Signature Requested” email

This setting allows administrators to control the visibility of sender and recipient details in the “Signature Requested” email notifications sent by Acrobat Sign. Customizing these settings can help manage privacy and reduce confusion for recipients.

---

Settings Explained:

• Hide the sender name and sender email – Removes the sender’s name and email from the “Signature Requested” email. This may be useful when agreements are sent on behalf of an organization rather than an individual.

• Hide the other recipient email(s) – Prevents recipients from seeing who else has received the agreement for signing. This can be useful for privacy reasons, especially in agreements involving multiple external signers.

---

Recommended Settings:

• Leave both options unchecked – Keeping sender and recipient details visible ensures clarity and transparency in the signing process.

• Enable “Hide the other recipient email(s)” only if needed – This may be useful in cases where privacy concerns arise with multiple external signers.

68. Save

Once all settings have been configured, clicking the Save button ensures that the changes are applied and stored in the Adobe Sign system.

Created with Tango.ai