> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/collaboration.md).
# Collaboration
Work on knowledge base content together with your team
## Commenting
Leave Google-docs style comments on articles to leave or request feedback on content.
In comments you can:
* Use rich text like bolds, italics, links, code, etc.
* Add attachments like images
* Tag other users on your team (and they'll receive a notification!)
* React to comments with emojis
You can click on the comment icon at the top of the doc to view historical comments that were already resolved.
## Collaborative Editing
Work on articles together in real-time. You'll be able to see an indicator in the editor if your teammates are editing content at the same time as you.
---
# 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.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/collaboration.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.
