> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/playbooks/share-a-playbook.md).

# Share a playbook

Share a playbook from the **Share** button at the top of the playbook page so teammates can see its runs, run it themselves, or help maintain it. You can share with individual people, with teams, or with everyone in the workspace, at one of three levels: **Can view**, **Can edit** or **Can manage**. Until you share it, a playbook is visible only to you.

## Who can share a playbook

The **Share** button appears for the person who created the playbook and for anyone given **Can manage**. Playbooks that Rhythms creates for you personally (for example the one behind your Command Center) cannot be shared.

## Share a playbook

1. Open **Playbooks** and click the playbook.
2. Click **Share** in the top-right corner.
3. Type a person's name or a team name in the search box and pick them. Add as many as you need.
4. Set a level for each: **Can view**, **Can edit** or **Can manage**.
5. To open the playbook to the whole workspace, change **Only invited users and teams** to **Everyone at \[your workspace]** and choose the level everyone gets.
6. Click **Notify** to save and tell the people you added, or **Share without notifying** to save quietly.

The playbook now appears in each recipient's **Your Playbooks** list, marked "Shared by" you.

## Permission levels

| Level      | What the person can do                                                                                                                           |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Can view   | Open the playbook, read its configuration and instructions, and see its run history and the documents it produced. Cannot run or change it.      |
| Can edit   | Everything in Can view, plus **Run now**, rename the playbook, edit its instructions, connections and model, and **Disable** or **Activate** it. |
| Can manage | Everything in Can edit, plus share the playbook and change or remove other people's access.                                                      |

Only the creator can delete a playbook, whatever level others hold. There is no separate Owner level and no ownership transfer: give a colleague Can manage and they can do everything except delete.

## Change or remove someone's access

1. Open the playbook and click **Share**.
2. Use the dropdown next to a person or team to change their level, or choose **Remove access**.
3. Click **Notify** or **Share without notifying** to save.

Someone whose access is removed no longer sees the playbook in their list. Runs they started remain in the run history.

## Copy a link to a playbook

Click **Copy link** at the top of the Share dialog. The link opens the playbook for anyone who already has access. It does not grant access on its own.

## Frequently asked questions

**Can I share a playbook with people outside my workspace?** No. Playbook sharing is limited to members of your workspace.

**If I change a shared playbook, do others see the change?** Yes. Everyone with access sees the current configuration and instructions; there is no separate publish step.

**Can a viewer run the playbook?** No. Running requires Can edit. Give them Can edit if they should be able to trigger runs.

**Can teammates make their own copy of my playbook?** There is no copy button. They can ask the assistant to "create a playbook like ‹name›", which uses yours as a starting point without changing it.

**What happens to a shared playbook when its creator leaves?** The playbook keeps running and stays shared, but only the creator can delete it. Before an account is deactivated, ask the creator to give a colleague Can manage so someone can keep maintaining it.

## Related articles

* [Create and run a playbook](/playbooks/create-and-run-a-playbook.md)
* [Share a document](/documents-and-library/share-a-document.md)
* [Create and manage teams in Rhythms](/workspace-settings-and-administration/team-users-and-access/create-and-manage-teams.md)
* [User management in Rhythms](/workspace-settings-and-administration/team-users-and-access/add-and-manage-users.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/playbooks/share-a-playbook.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 `build a script that syncs our docs to a CMS` 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.