> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/catalyst-tools/community-review-module/due-diligence.md).
# Due Diligence
Completing Due Diligence
**User that didn’t have DD verified in previous funds**
1. Once you subscribe to be a Reviewer, you will see a notification at the top of the page indicating that you need to complete the Due Diligence (DD) process
Accessing the DD Portal:
2. Click the "Complete verification" link to proceed
3. This will redirect you to the Due Diligence portal (Sumsub) where you can complete the necessary checks. If any issues occur, please raise a ticket [here](https://catalystiog.zendesk.com/hc/en-us/requests/new)
2. Follow the instructions on the portal to finish the DD checks
3. Returning to Community Review module page:
1. Once completed, return to the Community Review module
2. Refresh the page to update your status
4. Participating as a Reviewer:
1. After completing the DD process and refreshing the page, you will be able to participate as a Reviewer in the current fund
**User that had DD verified in previous funds\***
1. Once you subscribe to be a Reviewer, you will see the status “approved” in DD status which means that DD verification is already completed.
\* Only users who registered in the [Catalyst App](http://app.projectcatalyst.io/) using the same email address previously used in Ideascale for earlier funds will be automatically verified through due diligence (DD). If a user was previously DD verified but registered in the [Catalyst App](http://app.projectcatalyst.io/) with a different email, they must re-register in the[ Catalyst App](http://app.projectcatalyst.io/) using the correct email and then create their account in the module again.
---
# 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.projectcatalyst.io/catalyst-tools/community-review-module/due-diligence.md?ask=&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.
