> For the complete documentation index, see [llms.txt](https://kycdocv2.faceki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kycdocv2.faceki.com/quick-guides/sdk-settings.md).

# SDK Settings

{% embed url="<https://www.youtube.com/watch?feature=youtu.be&v=W44LejBvNDM>" %}
SDK Setting Video
{% endembed %}

### SDK Setting Steps

![](/files/IQHeYV0fRaR0Z7ZUwb5E)

Step 1: [Access to workflow](https://apps.faceki.com/workflow/documents-to-verify) → Verification Workflow → Documents to Verify → Choose the number of documents.

<figure><img src="/files/8sUDxXN9OtTGolxvywZ7" alt=""><figcaption></figcaption></figure>

Step 2: Choose which type(s) of document you want your users to verify. You can choose from a range of options depending on your specific needs.

<figure><img src="/files/620ORJReZJi71J5j1Y2T" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Depending on the selected number of documents chosen in step 1, you can choose different document types as shown above, in the order that you want your users to capture them.
{% endhint %}

<figure><img src="/files/wUGfnNVt1o14lEXOOKC9" alt=""><figcaption></figcaption></figure>

Step 3: Add a custom message under each verification option. This message will be displayed to your users after they complete the verification process. You can also insert a link that your users will be redirected to depending on their verification results. This allows you to customize the user experience and provide specific instructions or guidance as needed. You can use the following link for redirection: <https://apps.faceki.com/Workflow/Verification-Screens>.


---

# 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://kycdocv2.faceki.com/quick-guides/sdk-settings.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.