> For the complete documentation index, see [llms.txt](https://docs.mogoplus.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mogoplus.ai/mogoplus/getting-started/categorise-your-way.md).
# Categorise your way
Here you can understand how to modify/update the default categories to the categories that you need and a lot more
### Review/Modify categories (Optional exercise)
Choose the category/row you would like to change
Click on the edit icon and change the category name to the name you need
Scroll down to the bottom of page and click Save
Click "Save" on the confirmation pop-up
Client Categorisation mapping will be updated
**Note**: If the product is other than GoCat, you will see additional options to update the category mapping and the corresponding insights.
---
# 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.mogoplus.ai/mogoplus/getting-started/categorise-your-way.md?ask=&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.
