Acrobat Sign - General
Your feedback is essential to helping us shape the future of Acrobat Sign. That’s why we have partnered with UserVoice, a third-party service, to create this site to hear your ideas and suggestions. Here, you can send us ideas for new features you’d like to see or report bugs that are getting in your way.
The UserVoice feedback pages are for feature requests and bug reports only. If your submission is not a product feature, suggestion, or product question, it may be removed. Only upload content that you have permission to use and refrain from posting personal information (home address, phone number, email address, serial number, or credit card information). Spam, content that promotes illegal activity, vulgar or abusive language, or fraudulent or phishing links are not allowed on this platform.
UserVoice is a third-party platform for product feedback. The Acrobat Sign team regularly reviews ideas and incorporates them into product planning discussions. We can’t guarantee specific features or development timelines, but we read every suggestion and respond where we can. Please note that feedback is voluntary, and if you provide feedback, you give Adobe the right to use it without restrictions.
For all other questions and discussions, visit the Adobe Acrobat Sign forum.
Submit feature requests and bug reports to our product teams via this UserVoice site. You can also look at ideas and issues that other users have submitted and vote for ideas you like.
How it works:
- Select the feedback forum for your product.
- Browse ideas and vote for the ones you like.
- If your feature idea or issue is not listed, post it.
110 results found
-
Feature
Include a feature that allows a document in progress to be modified by the initiator or enable Admin to troubleshoot / resolve from backend
1 vote -
Change DOB requirement to "over 18" checkbox
Applies to all Adobe Terms and Conditions. There's no legitimate reason to ask for a user's date of birth in the terms and conditions.
If the purpose is to make sure a user is over 18 to purchase and understand the terms, as suggested here (https://community.adobe.com/t5/creative-cloud-services-discussions/why-am-i-being-required-to-give-my-date-of-birth/m-p/12320143), then provide an "over 18" checkbox.
As a user, my DOB shouldn't be used for other purposes.
2 votes -
Rollout Adobe Sign by default on each SharePoint site
Currently the Adobe Sign feature needs to be added to each SharePoint Site manually.
It should be possible to add the Adobe Sign feature by default to every new created SharePoint site.
1 vote -
Adobe Sign feature on SharePoint Sites using Microsoft 365 Groups
The Adobe Sign feature can be added to SharePoint sites manually. By default, users with SharePoint Membership rights (“Users in default members/owners group with Edit permissions”) and a valid Adobe Sign license can use this feature. If you transfer the users to the Microsoft 365 Group, they technically keep their membership status on the SharePoint site, but they can`t use the Adobe Sign feature anymore, as the standard setting of Adobe Sign states, that only Members (“Users in default members/owners group with Edit permissions”) can use Adobe Sign.
In this case the User or Admin must change the settings of…
1 vote -
Remove the word "agreement"- replace it with "document"
Remove the work "agreement" in the whole Adobe Acrobat Sign and replace with "document". Because it is not just used to sign an agreement .
4 votes -
Control user email notifications in general account settings as an administrator
it is only possible to make the adjustment for each user, but imagine if you have 150 users and not all of them many times can make the changes. Ideally, the account administrator can give you general support in turning off all email notifications.
6 votes -
Have a "test" button that doesn't cost for sending.
Because Adobe sign is filled with so many features, sometimes it's hard to know if you're selecting the right boxes to have the customer sign/fill out. Especially, when doing workflows and you're wanting the form to go to multiple people and in a specific order. I would like a "Test" button that will allow you to go through the process (with the same email in all slots so Adobe knows you're not trying to cheat the system). That way the person that is doing the test runs has received all the emails, in the order they would normally go out,…
10 votes -
Enable Digital Signatures on Web Forms
Add the possibility, in Web Forms, to use Digital Signatures, not only Signatures.
In the "Use digital signatures" page, the very first row states 'The Adobe Sign Digital Signature workflow is available to all levels of service'. To be true, that should also be available to Web Forms.7 votes -
Adobe Sign send in bulk: Preview before send
When using the 'send in bulk' feature (formerly Mega Sign)the preview should give you a view of at least what one of the sent requests will look like (pre-populated with details pull from spreadsheet). Ideally also some information on how many users it will send to and which fields will be populated. E.g. if there is a mapping error it would be easier to spot on the preview and fix the spreadsheet. Possible a second preview page before sending.
3 votes -
Finder extension/plug in on MAC
It would be nice if Adobe Sign had a finder plugin for MACS. That way we can quickly see an option to Sign with AdobeSign by right clicking on a PDF. Quickly taking us to our AdobeSign account, with the PDF already uploaded and ready to send out.
Dropbox (HelloSign) already has this feature and it is tempting and will only get more tempting once they add more feature.
1 vote -
Ensure default and available authentication methods are read from the selected group when the option "Users in multiple groups" is enabled
When enabling the Users In Multiple Groups functionality and a sender selects a Send from group all the associated Group Setting should be used. Currenty the following settings are defined by the senders primary group and not the selected Send from group:
• Enable the following identity authentication methods for recipients
• By default, use the following methodThis makes it possible for a sender to select a group which is intended for signatures meeting specific regulatory requirements (with a set of allowed authentication methods) and then still be able to select a non-approved authentication method as these are read…
3 votes -
Allow edits to envelope sent in bulk format and not just individual sent envelopes
I need the ability to edit any envelopes sent in Bulk, right now I can only do it when sending individually.
1 vote -
Populate Dynamics 365 XML fields for Adobe Sign Agreement Templates
The main goal is to be able to send a quote or invoice that contains a table/ list of products out for signature using the 'send for signature' workflow in Dynamics 365. The current adobe sign field mappings using {{}} does not allow table generation however the native Dynamics 365-word template generation process that uses XML fields does.
It would be good if word document templates uploaded to the agreement template record in the D365 adobe sign module would have the xml fields automatically populated during the 'send for signature' process. This means more complete table generation could be handled…
6 votes -
Allow the users to manage templates for shared accounts
We make heavy use of templates within our 300-user account.
We create the templates under an Adobe Sign "service account", and share access to that service account with others within a department (e.g. Customer.Service@example.com). End-users within CSD access the shared account using the "Switch Account" feature.
Currently, Adobe Sign only allows you to manage transactions related to the shared user. You cannot edit templates under that shared user's account.
That means is that if we want to create more templates (or edit an existing one), we have to teach our end-users to sign out of Adobe Sign, and back…
11 votes -
Allow sender to specify number of required signers within recipient group
At the moment when any member of a Recipient Group signs, they sign on behalf of their whole group and the document moves onto the next Recipient.
There are situations where the Sender needs signatures from any 2 members of the recipient group. Or, from 3 out of 5 members, etc. For example, a Payment Authorisation that needs signatures from any two Board members.
The current workaround is not ideal because it involves splitting signers into subgroups, which doesn't always work operationally.
Please consider (on the Send screen) allowing the Sender to specify the number of members within the recipient…
4 votes -
Reusable recipients list
It would be nice to have a template-like solution where the Recipient emails can be inputted automatically. A project usually has a static group of signers. Different projects, different signers. When there are multiple projects going on at the same time, it would be a huge time savings to be able to select Project A and all the email addresses are filled in by the system. Select Project C and a different selection of emails are inputted automatically.
31 votes -
Allow Audit Reports to be Attached to Each Document When Downloading Individually
It would be a tremendous help in keeping us compliant with FDA 21 CFR Part 11 if the Audit Report for a transaction were to be attached to a document when a document is "downloaded individually" from a transaction with multiple documents. It's possible to download the Audit Report as a separate document, but associating that report with a signed document without ruining the certification is difficult to manage.
7 votes -
Assign field template in a workflow (automatically predefined or as part of the workflow)
It would be ideal if an existing field layer template could be assigned to a document in a workflow. Currently one must run the workflow and remember to apply the correct template manually so that the signature fields appear. For example, a prefilled Purchase Order needs to be sent for two signatures that are applied automatically by the template prior to sending. Others have asked for this in the Community.
1 vote -
Allow APIs to send agreements with pre-fill fields out for signature
At the moment, if your agreement has any fields where the "Assigned To" is set to "Sender (prefill)" you cannot use the Adobe Sign APIs to send the document for signing. Instead, the document gets stuck in the "Waiting for you" area. If you change the "Assigned To" to something else and run the same API calls, Adobe Sign automatically sends out the signature requests. See the following example linked below:
Like in the above-linked example, we have forms that are automatically distributed by a background process. If that fails, or for some reason another instance of that agreement…
9 votes -
Loss of Functionality in Recent Upgrades to Adobe Sign vs Classic Adobe Sign Experience
When I send out contracts for signature the first step is for the person at our firm who is requesting the contract to act as approver. It then goes to the signatory(ies). For whatever reason, the e-mail from Echo Sign often ends up in a junk mail or clutter folder. In those cases when enough time has elapsed, I send a Reminder via Adobe Sign to the requestor/approver to be in touch with the signatory(ies) to see what is happening. The requestor/approver is the person with whom the signatory(ies) is/are used to dealing with and recognize their e-mail. Prior to…
6 votes
- Don't see your idea?