# Introduction

UAEPASS provides a **"Hash Signing"** feature for digital document signing, ensuring a more secure method to sign PDF documents without the need to send them outside the organization's premises.

**Here's how it works:** 

When a user logs into a document signature portal or application through UAEPASS authentication, the entity requests the signing of a document from UAEPASS. The entity sends the document's hash to UAEPASS and UAEPASS signs the hash of the document to send it back to the entity in PKCS#1 format. Entity should embed the signed hash back into the document in PKCS#7 format. At the end user can view and download the signed document.

Below is the high-level architectural diagram of UAEPASS Hash Signing:

![Fig 1: High Level Architecture of UAEPASS Hash Signing](/files/-MkkRuwuVnYyGIsnSZpe)

![Fig 2 : Hash Signing Work Flow](/files/djGAPI8W8oqwudYXcAqf)

![Fig 3: Hash Signing Flow](/files/gnGgK2smrpEZceidNwmF)


---

# 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://docs.uaepass.ae/feature-guides/signature-integration-guide/hash-signing/introduction.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.