> 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/milestone-module/milestone-module-roles-and-responsibilities/catalyst-team-reviewer-using-the-milestone-module.md).

# Catalyst Team Reviewer using the Milestone module

## Actions that a Catalyst Team Reviewer can carry out in the module

Catalyst Team Reviewer can carry out the following actions using the [Milestone module](https://milestones.projectcatalyst.io/): 

* Assign reviewer
* Review milestones and PoA

### Catalyst Team Reviewer can assign reviewer

Catalyst Team Reviewers can assign Milestone Reviewers by filling reviewer allocations in the proposals listing page or on the project dashboard. 

The Catalyst Team Reviewer does this at the beginning of the onboarding stage. 

### Catalyst Team Reviewer can review milestones and PoA

From F11, each FP should be reviewed by Milestone Reviewers. It is the next key step in transitioning the responsibility towards the community.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.projectcatalyst.io/catalyst-tools/milestone-module/milestone-module-roles-and-responsibilities/catalyst-team-reviewer-using-the-milestone-module.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.