> 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/profile-page.md).

# Profile page

1. Navigate to the Profile page  by clicking “Profile” in top-right corner
2. Here you can check:
   1. Your personal information (username, CatalystID, email address, registration date, account status)
   2. Reviewer information - in this part you may find information on Reviewers levels you were assigned to (remember to use the same email address you used in Ideascale once you register in the [Catalyst App](http://app.projectcatalyst.io/), only in this way the system will match your previous performance). You will see there also information to which category you subscribed to be a Reviewer. Reviewers who subscribed to be a Reviewer in Catalyst and Midnight categories, will have two anonymized IDs.
   3. Due Diligence status
   4. Password update settings
3. Please make sure you have status Active in Personal information, Reviewer information and status Approved in Due Diligence part


---

# 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/profile-page.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.