# Automate E-Signature & Sign in Person

<figure><img src="/files/btnaov6rdLcrYVPEs7gr" alt=""><figcaption></figcaption></figure>

### Understanding the Overall Schema

Outlined above is the generalized process from start to finish users will take to generate an S-Sign Request in a screen flow for Sign-In-Person Use Cases.&#x20;

The process goes as follows:

1. **Collect Data** that will be used for document generation (S-Sign Enabled Template + Object Record)
2. **Generate the document** from the collected data
3. **Prepare the Envelope** the Generated Document will be stored in
4. **Seal the Envelope** in preparation to deliver the request
5. **Display** the signing link to the active signer.

This process is not all that different from a Screen Flow that generates and delivers an S-Sign Request. The key difference is an ommission of the Send Email Invocable action and instead using a screen to display the signing link to the active signer.&#x20;

***

### Phase 1: Configure the Prepare Envelope Action

<figure><img src="/files/FdIyZERkH97TuacuTmbc" alt="" width="477"><figcaption></figcaption></figure>

After the data has been collected and the document has been generated, users will begin to package the document into the envelope. For In-Person Signing Experiences, the **Sign In Person** option must be included and set to **True.**

***

### Phase 2: Configure the Screen Component&#x20;

<figure><img src="/files/soaplPFh0Sj5NhgSKKb0" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/BybyypupnoYAX4RsRI0I" alt=""><figcaption></figcaption></figure>

After the envelope has been sealed, add a screen component to display a message and signing link to the active signer.&#x20;

1. Use a **Display Text Component** within the screen
2. Add the **display text** with a **Link**&#x20;
3. Ensure the **Link URL** is defined as the **Seal Envelope Invocable API Name.signingLink**, for example: {!Seal\_Envelope.signingLink}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sdocs.com/s-sign/automation-and-envelope-lifecycle/automate-e-signature-with-flow-builder/automate-e-signature-and-sign-in-person.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.