> 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/guides.md).

# Guides

Explore guides for collaborating on documentation with your team

Collaborate on content with your team. These guides cover change requests, reviews, comments, and access.

#### Explore

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-code-branch">:code-branch:</i></h4></td><td><h4>How to collaborate on change requests</h4></td><td>Learn how your team can work together using change requests</td><td><a href="/docs/guides/editing-and-publishing-documentation/how-to-collaborate-on-change-requests.md">How to collaborate on change requests</a></td></tr></tbody></table>

#### Quick guides

<details>

<summary>How do I set up access for my team?</summary>

Choose roles and permissions that let your team collaborate safely.

This guide covers inviting teammates, managing access, and organizing teams.

<button type="button" class="button secondary" data-action="ask" data-query="How do I set up access for my team in GitBook? Show me how to invite teammates, assign roles and permissions, and organize teams. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I create and merge a change request?</summary>

Change requests let you propose and safely publish content updates.

This guide covers creating changes, requesting a review, and merging approved work.

<button type="button" class="button secondary" data-action="ask" data-query="How do I create and merge a change request in GitBook? Show me how to make changes, request a review, and merge approved work. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I review a change request?</summary>

Reviewers can compare edits, give feedback, and approve changes.

This guide covers reviewing diffs, requesting changes, and approving a change request.

<button type="button" class="button secondary" data-action="ask" data-query="How do I review a change request in GitBook? Show me how to compare diffs, leave feedback, request changes, and approve a change request. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>

<details>

<summary>How do I discuss and resolve feedback?</summary>

Comments keep questions and feedback connected to the relevant content.

This guide covers adding comments, mentioning teammates, and resolving threads.

<button type="button" class="button secondary" data-action="ask" data-query="How do I discuss and resolve feedback in GitBook? Show me how to add comments, mention teammates, reply to threads, and resolve comments. Include links to the relevant docs pages." data-icon="gitbook-assistant">Open guide</button>

</details>


---

# 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/guides.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.