> For the complete documentation index, see [llms.txt](https://docs.blocksquare.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocksquare.io/faq/marketplace-operators/user-management.md).

# User management

<details>

<summary><strong>What criteria is used to "whitelist" a user in addition to KYC?</strong></summary>

Who gets whitelisted on your marketplace is at the sole discretion of you as the marketplace operator. Some marketplace operators wish to run "private investment clubs" with complex eligibility criteria, whilst others opt to whitelist any user who meets basic KYC criteria.

On the back office level, we currently support two options to enable the above:

1. anyone who passess KYC is auto whitelisted for the marketplace, and
2. all users who pass KYC need to be confirmed by the marketplace admin

*Note: As we develop new functionalities, more complex features should become available for marketplace operators to efficiently administer their investor communities.*

</details>


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.blocksquare.io/faq/marketplace-operators/user-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
