> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/runbooks/concepts/collaborating-with-the-team.md).

# Collaborating with the team

The platform supports team collaboration through shared [Runbooks](/runbooks/concepts/runbook-format.md) and coordinated execution.

## Adding Collaborators

Collaborators receive same access as the primary user. You can add the collaborator from the chat interface of the Runbook. Simply navigate to the "Share" button, search for a team member and Invite. The invited member will receive an email with the link to the Runbook. You can also copy the link and share with your team member directly after adding them as a collaborator.

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FeG01fHAMpa2QjJH1f2gf%2FScreenshot%202025-09-21%20at%209.55.08%E2%80%AFPM.png?alt=media&amp;token=885bbd7b-b104-4541-90a3-da65c2b9a87e" alt=""><figcaption></figcaption></figure>

### Collaborator's access

All collaborators see the same Runbook version. All the changes are immediately visible to all team members. The collaborators can also view the execution history, edit the Runbook or execute any step.

## Best Practices for Teams

* Establish clear ownership for Runbooks
* Use descriptive names and documentation
* Regular reviews of generated changes
* Coordinate execution timing
* Share learnings through global context


---

# 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.aviator.co/runbooks/concepts/collaborating-with-the-team.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.