> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/v1/teamwork/share-between-spaces.md).

# Share Rules Between Spaces

## How to share rules between spaces?

To share a rule, click the ![](https://content.gitbook.com/content/dv9UprVu3KjO5la255ws/blobs/z3Hu2Jme5f7ZCJpmSZLf/image.png) button, then click the <img src="https://content.gitbook.com/content/dv9UprVu3KjO5la255ws/blobs/XddfjeDkhaZJvhGTDTLL/image.png" alt="" data-size="line"> button. When clicked, the full menu of options is displayed.

<figure><img src="https://content.gitbook.com/content/dv9UprVu3KjO5la255ws/blobs/6pdqRvkQSZDMP9TTGBIE/image.png" alt=""><figcaption></figcaption></figure>

### Clone to Space

Clone rule to selected Space with a new rule ID. This means the original rule and the clone are independent of each other.

### Share with Space

When you share a rule with another space, the rule will be accessible in both the original Space and the one it was shared with. Nevertheless, it is still the same rule. If you change the rule in one Space, the changes will be reflected in the other Space as well.

### Move to Space

The rule will be removed from the original Space to the selected Space. It will keep its rule ID but will no longer be accessible from the original Space.


---

# 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.decisionrules.io/doc/v1/teamwork/share-between-spaces.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.
