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

# Spaces

Owners and admins create and manage the organization's spaces in **Spaces** in the Admin Console. Each space is public or private.

|                        | Public                                | Private                            |
| ---------------------- | ------------------------------------- | ---------------------------------- |
| Who's in it            | Every member of the organization      | Only people an owner or admin adds |
| Who sees it in the app | Everyone                              | Only its members                   |
| Permission             | The space's default: Writer or Reader | Chosen when adding each person     |

Owners and admins can see and manage all spaces in the Admin Console, including private ones. Whoever creates a space gets **Admin** in it.

## Create a space

1. Open **Spaces** and click **Create space**.
2. Enter a **Space name**.
3. Choose **Visibility**: **Public** or **Private**.
4. For a public space, choose the **Default permission for joiners**: **writer** (can create and edit) or **reader** (view only).
5. Click **Create**.

{% hint style="warning" %}
You can't change visibility after the space is created.
{% endhint %}

## Public spaces

Every member is added to a public space automatically, both when the space is created and when someone new joins the organization. Members can leave and rejoin.

Use public spaces for company-wide content, such as a wiki or announcements.

## Private spaces

Only an owner or admin can add people to a private space. Other members don't see it in the app.

Use private spaces for a team or project.

## Manage who's in a space

Open a space in **Spaces**.

* **Add members:** click **Add members**, pick people, choose a permission and click **Add**. **Reader** is selected by default.
* **Change permission:** set a person to **Reader**, **Writer** or **Admin**.
* **Remove:** select people, click **Remove selected** and confirm.

{% hint style="info" %}
Anyone who's a Writer or Admin in any space counts as an editor for billing.
{% endhint %}


---

# 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://doc.anytype.io/anytype/anytype-for-business/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.