> 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/fund10-docs/project-onboarding/funded-proposers-fp/statement-of-milestones/how-to-use-the-milestone-module-in-f10/approval-of-the-proof-of-achievement/using-the-milestone-module/roles-and-responsibilities.md). # Roles and responsibilities The overall flow of processing a milestone relies on multiple participants. The following is a list of the participants' roles and their respective responsibilities: 1. Funded Project (FP) - can submit and resubmit milestones and PoA. 2. Milestone reviewer - can review milestones and PoA 3. Catalyst Team reviewer - can review milestones and PoA 4. Catalyst Team sign-off user- can provide final approval of milestones and PoA, assign reviewer, review milestones and PoA 5. Catalyst Team system admin - Admins can assign reviewers/proposals, review/approve milestones and PoA and can also export data in CSV format to create funding files. --- # 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/previous-funds/fund10-docs/project-onboarding/funded-proposers-fp/statement-of-milestones/how-to-use-the-milestone-module-in-f10/approval-of-the-proof-of-achievement/using-the-milestone-module/roles-and-responsibilities.md?ask=&goal= ``` `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.