# Step-by-step User Journey

#### 1. By clicking the "Sign with Singpass" button on your portal, the user will be redirected to Singpass signing portal.

The following elements in the sample image below will be replaced with information provided to us during your [onboarding](/for-relying-parties/how-our-api-works.md):

* "*Login PDF Viewer Client*" will be replaced with your display name provided
* Your organisation's logo will be displayed beside the display name, instead of the placeholder image

![](/files/db5YjIT1XAyTm7RxvsBg)

#### 2. The user is required to verify their identity with Singpass before they can view the document. They will do this by performing a Singpass Log In with their Singpass App.

![](https://image.mux.com/0224WrueMbF3tqP456inX99UnYphFtFXLMSsOcfMiN8k/animated.gif?start=0\&end=3.933333\&width=640\&fps=30)

![](https://image.mux.com/ScS6tro518ZEOnRgBZRCNzzc11J018EwANJafdJzvePM/animated.gif?start=0\&end=5.553333\&width=640\&fps=30)

#### 3. Upon successful authentication, the user can begin reviewing the document.

The document name ("dummy.pdf") will be taken from the `doc_name` parameter provided in the payload when [initiating the sign request](/for-relying-parties/api-documentation/sign-v3/initiate-sign-request.md).

![](/files/BS4GYzem4DdxwTYloytj)

#### 4. In the field navigation panel, the user can easily locate the fields in the document that require their signature.

This panel is on the right of the desktop screen. For mobile users, it will be at the bottom.

![](https://image.mux.com/uwfDWl013eitl2uAY84VrhNwQ8RggeGVRLwROzrNZKsA/animated.gif?start=16.271\&end=18.351\&width=640\&fps=30)

#### 5. The user must review each field by clicking/tapping on them.

For mobile, the user can also tap the 'Mark as reviewed' button to review each field.

![](/files/txbvyuL5EYHYlOYi9NAH)

![](/files/s0CMOmkJQkie8ST8G8yL)

#### 6. The Sign button becomes active once all fields are reviewed.

![](/files/wwz2asP3NjJwgLE1S42E)

#### 7. When the Sign button is clicked, the user will be shown a QR code, which they should scan with their Singpass App on their mobile device.

It will also display a **match reference code** ("9736" in the example below)

![](https://image.mux.com/sxQ4Weh5QO52fv15FsE9v1OEX9sqd8kIa4Q5p8nKDcQ/animated.gif?start=0\&end=3.533333\&width=640\&fps=30)

#### 8. On their Singpass App, the user will select Approve or Reject.

They can also check the **Match reference code** to ensure they are signing the right document. 

![](https://image.mux.com/UJdgGDYCYEahtauHU4JTdtpwiDRbuYAaOveW7eKtTzA/animated.gif?start=0\&end=4.8\&width=640\&fps=30)

#### 9. Document is successfully signed! At this point, the user can return to your portal, or view their signed document first.

The user can view their signed document by clicking 'View Signed Document'.

![](/files/PJvHBhoi6YLbES6vwQ3T)

#### 10. At this point, the user can check signature details for added transparency and peace of mind.

The user will return to your portal by clicking 'Leave Sign Portal' as the final step, to complete the rest of the process (if any).

![](/files/fVP1uqZWWkfzHrsYyCjv)


---

# 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.sign.singpass.gov.sg/for-relying-parties/api-documentation/sign-v3/sign-portal/sign-portal.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.