> 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/current-fund/community-review/how-to-become-a-community-reviewer.md).

# How to become a Community Reviewer?

This page provides guidance to become Community Reviewer

In Fund15, the Community Review stage will take place within the [Community Review module](https://reviews.projectcatalyst.io/) - a new platform designed specifically to manage the Community Review and Moderation process. This module replaces Ideascale, which was used up to Fund13. Please follow this [user guide](/catalyst-tools/community-review-module.md) to get familiarized with this new platform.

**IMPORTANT**: If you are interested to become LV0, LV1 or LV2 in Fund15, you have to register in the [Community Review module](https://reviews.projectcatalyst.io/) during [submission window](/current-fund/fund-basics/fund-timeline.md)**.**


---

# 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/current-fund/community-review/how-to-become-a-community-reviewer.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.