> 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/previous-funds/fund13-docs/community-review/faq.md).

# FAQ

**How to identify my ID in the Ideascale?**

Anonymized ID can be found in your profile, it will be visible once proposals allocation is done. IMPORTANT NOTE: Allocations and anonymized ID are not visible on the mobile devices.

**I registered to become a Community Reviewer and participate in the Community Review stage but I don’t have any proposals allocated.**

During the proposal allocation process, an automated analysis is conducted on the reviewer registrations received. If you registered but did not receive any allocations or level assignments, it means the analysis detected unusual activity associated with your account, including the potential use of multiple accounts for the review process. Consequently, you have been automatically excluded from participating in this round of project reviews.

**I was LV1 Community Reviewer in the previous Fund but now I am moved to LV0, why?**

Eligibility thresholds and requirements changes between Funds. It is possible that you were eligible to be LV1 in the previous Fund but not in the current one. Please check in the previous section what are the requirements for the current Fund.


---

# 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/previous-funds/fund13-docs/community-review/faq.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.