Log in to the Acrobat Sign portal as an administrator.
What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Add, edit, and review active users
- Create function-focused users
- Review users who haven't completed verification
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup / Branding Settings
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Apply Adaptive Signature Draw scaling
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send Settings
- Show Send page after login
- Agreement creation experiences
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Create a copy (of an agreement)
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Populate form fields with identity-verified data
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Restrict access to shared agreements
- Show Send page after login
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
- System Requirements and Limitations
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Automatic field detection
- Drag and drop fields using the authoring environment
- Assign form fields to recipients
- The Prefill role
- Apply fields with a reusable field template
- Transfer fields to a new library template
- Updated authoring environment when sending agreements
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Checkbox group
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Field types
- Authoring FAQ
- In-app authoring environment
- Sign Agreements
- Manage Agreements
- Manage page overview
- Copy an Agreement
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
Control who can access Acrobat Sign by allowing only trusted IP address ranges for account users and integrations.
Allowed IP Ranges let administrators limit access to Adobe Acrobat Sign to trusted networks only. By allowing requests from known IP addresses and denying all others, you can reduce unauthorized access and enforce consistent security policies across your organization. This control applies before user authentication and helps protect regulated environments and critical roles. This setting does not affect the recipients of the agreement.
Why use IP allowlists
Allowed IP Ranges act as a deny-by-default gate in front of Acrobat Sign. A user or integration can sign in to the web application or call the API only when the request originates from an IP address included in the allowlist.
- Reduce unauthorized access by limiting logins to known corporate networks.
- Enforce a consistent access policy across all users in the account.
- Pair with SSO and MFA for layered security.
Before you start
- Work with your network team to collect the exact IP ranges you need. Use CIDR notation (for example, 203.0.113.0/24).
- Plan to add administrator networks first so you don't lock yourself out.
- Consider remote, emergency, or partner access and include those ranges as required.
- Understand if you intend to use third-party applications (Salesforce, etc.) or the Acrobat Sign mobile applications (from a sender perspective).
Configuration
Availability:
- Acrobat Standard and Acrobat Pro: Not Supported
- Acrobat Sign Solutions: Supported
- Acrobat Sign for Government: Not Supported
Access scope
- Web UI: Requests from IPs outside the allowlist are denied with: “Your account cannot be accessed from this computer. Please contact your support staff.”
- API: Allowed only when the “Allow these IP addresses to access the system via API” setting is on; if it’s off, API calls are denied—even from listed IPs.
- Certified Applications: Major integrations (for example, Microsoft, Salesforce) are allowed by default.
- The Acrobat Sign mobile applications fall within the scope of Certified Applications and are impacted by the controls that allow or deny access to the Acrobat Sign service.
Note that only connecting to Acrobat Sign as a user is impacted. Recipients are not.
- The Acrobat Sign mobile applications fall within the scope of Certified Applications and are impacted by the controls that allow or deny access to the Acrobat Sign service.
Configuration scope:
- Allowed IP Ranges can be configured at the account and group level.
- User access is defined by their primary group when group-level settings are applied.
- Integrations (Microsoft Dynamics, Salesforce, and the like) are allowed by default.
There are three settings that determine whether IP restrictions apply to browser access, API requests, and API-based clients such as mobile applications and integrations.
- Only allow access to the system from IP addresses that are listed below - Enables IP address restrictions and unlocks the allowlist configuration.
- If no IP ranges are listed when the page configuration is saved, this option is automatically cleared, and the feature is disabled.
- If this option is not enabled, IP address restrictions are not enforced, and any IP address can attempt to access the account through user authentication.
- When you define one or more IP address ranges, only authentication attempts to sign in to the Acrobat Sign user interface from those addresses are allowed.
- Only allow these IP addresses to access the system via API - Explicitly grants API access from the listed IP ranges.
- This option requires IP address restrictions to be enabled.
- When enabled, only API connections from the listed IP addresses are permitted to connect.
- If this option is not enabled, API requests are denied, even when the request originates from an allowed IP address.
- Always allow API access from Certified Partner Application IP addresses - Allows certified applications to bypass API IP restrictions.
- This option requires API access to be enabled.
- When enabled, IP restrictions are not enforced for certified applications, including Acrobat Sign mobile applications.
- Certified Partner Applications include Acrobat Sign-developed integrations such as Salesforce and SharePoint.
To apply IP restrictions consistently across browser access, mobile applications, and integrations, API access must be enabled, and certified application bypass must not be allowed.
How to configure an allowed IP range
Coordinate with your network team to obtain the proper CIDR IP ranges before attempting to configure the allow list.
Be sure to allow the IP range you are currently working from first.
-
-
Navigate to Security Settings > Allowed IP Ranges.
-
Enable the Only allow access to the system from IP addresses that are listed below option by checking the box.
-
Select Add (+).
-
Save the entry.
-
Repeat these steps for each additional IP range.
-
Save the page configuration when finished.
All configured IP ranges are listed under the control set in a scrolling list. Up to two CIDR notations are exposed at once unless you select a new pagination option through the More options icon.
Manage the allowed IP ranges:
To search for a specific CIDR notation in the list of configured ranges, type the CIDR notation into the Search field.
As you type, the exposed IP ranges are filtered to show only ranges that match the string as you type it in.
To edit a CIDR notation:
-
Search and find the CIDR notation.
-
Select the notation to be edited to expose the available actions above the notation list.
-
Select the Edit action.
The Edit interface opens, with the current CIDR notation highlighted. -
Enter the new CIDR notation.
-
Save the notation when done.
There is no challenge to saving the edit.
To delete a CIDR notation:
-
Search and find the CIDR notation.
-
Select the notation to be edited to expose the available actions above the notation list.
-
Select the Delete action.
AlertThere is no challenge to deleting the notation.
Double-check that you are deleting the correct notation, and be sure you aren't deleting the notation allowing you to connect to the Acrobat Sign service.
It's entirely possible to configure the application in such a way as to deny all access from external sources.
Best practices
- Treat the allowlist as a deny-by-default policy: only known ranges should be added.
- Include contingency ranges for critical roles, if permitted by policy.
- If implementing the change after deployment to end-users, communicate it in advance so they know how to request access if they are blocked.
- If you restrict API access, review whether certified applications should bypass IP restrictions based on your usage and security requirements.
Manage and maintain
- Review and update ranges when networks change (new offices, VPN changes, ISPs, or cloud egress).
- Keep a documented source of truth for approved ranges.
- Test with a small set of users before rolling out to a broader audience.
- If users are blocked, verify their current public IP and add the correct range, or temporarily turn off the control and re-enable it after correction.
Impact and limitations
- Restricting access by IP address can limit support for remote users unless their networks or VPN egress ranges are included.
- This control affects access to the web application and the API.
- Integrations are allowed by default unless explicitly configured otherwise through Acrobat Sign support.
- It is possible to configure the account in a way that blocks all external access. Plan and test carefully.