> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/collaborate.md).

# Collaborate and review

- [Change requests](https://gitbook.com/docs/collaborate/change-requests.md): Collaborate on content edits through change requests
- [Change requests screen](https://gitbook.com/docs/collaborate/change-requests/change-requests-screen.md): Learn about the dedicated change requests screen, which helps you browse, manage and review change requests before merging them and publishing them in your documentation
- [Change requests in a section](https://gitbook.com/docs/collaborate/change-requests/change-requests-in-a-space.md): Learn about collaborating on a single change request in a section — including how to review, resolve conflicts and merge
- [Merge rules](https://gitbook.com/docs/collaborate/merge-rules.md): Define requirements that must be met before change requests can be merged
- [Comments](https://gitbook.com/docs/collaborate/comments.md): Ask questions to your team or receive feedback on the content you create
- [Live edits](https://gitbook.com/docs/collaborate/live-edits.md): Edit pages in real-time with other collaborators
- [Notifications](https://gitbook.com/docs/collaborate/notifications.md): Receive notifications about new content, updates to your sections or changes in visibility
- [Member management](https://gitbook.com/docs/collaborate/member-management.md): Learn how to manage access to content for members of your organization
- [Manage or remove members](https://gitbook.com/docs/collaborate/member-management/invite-members-to-your-organization.md): Learn how to manage the members of your organization, including adding new admins and what to do if the only admin leaves your organization
- [Permissions and inheritance](https://gitbook.com/docs/collaborate/member-management/permissions-and-inheritance.md): Understand how permissions work in GitBook and how to control who can access and edit your content
- [Roles](https://gitbook.com/docs/collaborate/member-management/roles.md): A breakdown of every role in GitBook — what each one can do, and how to use them to control access across your organization
- [Teams](https://gitbook.com/docs/collaborate/member-management/teams.md): Teams are a great way of grouping members within your organization
- [Inviting your team](https://gitbook.com/docs/collaborate/share.md): Learn how to invite teammates and other stakeholders to your GitBook organization as members or guests so they can collaborate on your content
- [Guides](https://gitbook.com/docs/collaborate/guides.md): Explore guides for collaborating on documentation with your team


---

# 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://gitbook.com/docs/collaborate.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.
