> 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

- [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. This setup provides a high-assuran
- [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.


---

# 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 dynamically by asking a question.

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.