> For the complete documentation index, see [llms.txt](https://docs.uaepass.ae/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uaepass.ae/guidelines/use-cases/standard-digital-signature-scenarios-for-service-provider-use-cases.md).

# Standard Digital Signature Scenarios for Service Provider Use Cases

Below is the list of use case scenarios described briefly for service providers to choose as per business requirements.

<table><thead><tr><th>Use Case No</th><th width="140">Sub-Category</th><th width="136">Pre-Requisite</th><th align="center">Acceptable SOP Types</th></tr></thead><tbody><tr><td>2.1.1</td><td>Single signer Digital signature flow</td><td>User with required certificate (Advanced/Qualified) signs the document.</td><td align="center">SOP2 (Advanced)/SOP3 (Advanced/Qualified) signing capability.</td></tr><tr><td>2.1.2</td><td>Multiple signer Digital signature flow</td><td>User with required certificate (Advanced/Qualified) signs the document.</td><td align="center">SOP2 (Advanced)/SOP3 (Advanced/Qualified) singing capability.</td></tr></tbody></table>

Below are the detailed use case scenarios to choose from, as applicable for each business scenario.

**Please make sure to highlight the use case no in your submitted use case scenarios diagram.**

### **2.1.1 Single signer Digital signature flow**

<figure><img src="/files/mLxnxjPppI7TZ88X5xLe" alt=""><figcaption><p><mark style="color:green;">Digital Signing - Single User</mark></p></figcaption></figure>

### **2.1.2 Multiple signer Digital signature flow**

<figure><img src="/files/pBwFpRaNDQxnJNPCm4uu" alt=""><figcaption><p><mark style="color:green;">Digital Signing - Multiple Users</mark></p></figcaption></figure>


---

# 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://docs.uaepass.ae/guidelines/use-cases/standard-digital-signature-scenarios-for-service-provider-use-cases.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.