Skip to main content
rebeccag76048937
rebeccag76048937
Participant
October 16, 2017
Answered

Force users to sign in to sign a document

  • October 16, 2017
  • 1 reply
  • 2563 views

We are using SharePoint with Nintex to automate document signing. The problem is that the URL it sends is completely anonymous. I'm wanting to find out how we can lock it down and force the assigned email address to login with their verified email address in order to view and sign the documents (only the documents for them). This will stop confidential documents being accessed by people that shouldn't see them.

The documents are internal only, e.g. for everyone to sign off on a new process or expenditure etc.

Anyone know if this is a possible setting or are we stuck with security by obscurity?

This topic has been closed for replies.
Correct answer ScottCarter

Greetings!

For users within your account, you can force them to authenticate to Adobe Sign before signing.

The setting can be configured by an Admin (at the Account or Group level) here: Account > Account Settings > Security Settings > Signer Identity Verification

1 reply

S
ScottCarterCorrect answer
Participating Frequently
October 16, 2017

Greetings!

For users within your account, you can force them to authenticate to Adobe Sign before signing.

The setting can be configured by an Admin (at the Account or Group level) here: Account > Account Settings > Security Settings > Signer Identity Verification

    rebeccag76048937
    rebeccag76048937Author
    Participant
    October 27, 2017

    Awesome, thanks!

    So the anonymous link will then only be anonymous to users who are outside of the account?

    S
    ScottCarter
    Participating Frequently
    October 30, 2017

    Thank you, this is super helpful

    Can you change the default behaviour for external recipients, or this is always the same and set by Adobe?


    That's a bit of an open ended question and depends on how you understand the ideas of the default behaviors and what properties are attached to which objects in the system, so I'm going to generalize.

    There are a few things that you can change in terms of how an external party can interact with your agreement (delegation, style of signature application, second factor authentication method), but only things in terms of interacting with your agreement and how your agreement is "edited".

    Ideas like enforcing a status (like requiring a user to have an active account so they can log in to authenticate) are reserved for the userID and the entity that governs that userID (the Group/Account the user is in) when applicable.

    The idea of requiring an external user to authenticate to Adobe Sign walks the line between the object you own (the agreement and its' properties) and an object you don't (the external userID and their status in the system).

    That said, the ability to do so is likely possible, and if it's important to your business process, I suggest posting an idea (or any other idea!) to the ideas.echosign.com site for our product team to review. 

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices