Force users to sign in to sign a document

[rebeccag76048937]

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?

[ScottCarter · Accepted solution]

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]

Awesome, thanks!

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

[ScottCarter]

The link itself does not change, but how the recipient is understood and treated does.

Each signing link is directly tied to a userID, which is (effectively) indicated a unique email address (It's more complex than that, but that level of detail doesn't help clarify your question)

Because recipients (emails) within your organization are under a specific rule set that dictates a specific behavior, when they click the link, the behavior is triggered.

Recipients external to your account are under a different set of rules.

If they also happen to be in an Adobe Sign account, then the rules for signers in that account will apply to them.

If they are in no account (The vast bulk of people), then the default rules apply.  The signature link is still directly tied to the userID (email) in all cases for audit-ability,

[rebeccag76048937]

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?

[ScottCarter]

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. 

[patricek35877823]

Hi - I'm posting this here since it seems more active.

The use case we are exploring involves using Adobe sign to serve signable documents for non-Adobe Sign users.

Here is the use case:

We need to build an app that displays the signable widget and allows external users to sign.

Our app collects more data, pre-fills some widget fields with our custom validated data.

Our app presents the widget on our web page where the user finalizes and signs.

Of course she signs with her verifiable e-mail address and is prompted (via mail) to verify her identity.

She then receives a reply with the final product.

Our app can then (via the api) display her tracking status and even provide access to the final product.

Is this possible? The idea is not to force our clients to provision separate Adobe Sign accounts.

Thank you in advance.

Patrice