> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/s-sign/advanced-signer-scenarios.md).

# Advanced Signer Scenarios

- [S-Sign Authentication and Signer Links](https://help.sdocs.com/s-sign/advanced-signer-scenarios/s-sign-authentication-and-signer-links.md): This page details the different signing links that are produced via our S-Sign product and how generation methods, licensing, and permissions can affect their output.
- [Setup multi-Signer Routing Rules](https://help.sdocs.com/s-sign/advanced-signer-scenarios/setup-multi-signer-routing-rules.md)
- [Setup Multi-Document Generation](https://help.sdocs.com/s-sign/advanced-signer-scenarios/setup-multi-document-generation.md)
- [Signer Authentication](https://help.sdocs.com/s-sign/advanced-signer-scenarios/signer-authentication.md): S-Sign ensures secure document execution by combining unique access links with customizable identity verification layers. As a 100% native Salesforce app, all authentication data and signing processes
- [PIN Verification](https://help.sdocs.com/s-sign/advanced-signer-scenarios/signer-authentication/pin-verification.md): Enable S-Sign templates to require the current active signer to engage the signer experience.
- [CAC/PIV Verification](https://help.sdocs.com/s-sign/advanced-signer-scenarios/signer-authentication/cac-piv-verification.md): This guide outlines how to configure CAC (Common Access Card) and PIV (Personal Identity Verification) authentication for S-Sign using Okta as the Identity Provider.
- [Translations](https://help.sdocs.com/s-sign/advanced-signer-scenarios/translations.md): Translating the S-Sign signer experience ensures that your customers have a seamless experience in their native language when signing documents.
- [S-Sign Troubleshooting](https://help.sdocs.com/s-sign/advanced-signer-scenarios/s-sign-troubleshooting.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/s-sign/advanced-signer-scenarios.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.