> 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/space/spaces.md). # Space Introduction Agile software development often works in end-to-end delivery teams. To support this thesis, we plan to create project sites where each team will have its business rules under its management. {% embed url="" %} Spaces allow you to work together with your team in DecisionRules and to create the rules together. It's easy and time-efficient to edit or create your rules. :rocket: ### Getting started After logging in, the rule list is displayed. The active space is shown in the top-left corner. To view its details, click **Space** in the left-hand menu and the **Space Info** screen will open.

{% hint style="info" %} The number of spaces depends on[ **the product plan**](https://www.decisionrules.io/pricing/public-cloud) {% endhint %} ### Change your space If you want to change your space you are in, click on the Space selector, modal window will show up with your spaces you can choose from.

### Create new space Create a new space from the **Select Space** modal using the "**+Space**" button. Select the owner (you or an eligible organization), enter the space name, and confirm by clicking **Create**. The space is created instantly.

--- # 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/space/spaces.md?ask=&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.