> For the complete documentation index, see [llms.txt](https://guide.graphqleditor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.graphqleditor.com/graphql-editor/readme/workspaces.md).

# Workspaces

Workspaces are used to organize projects. Each workspace consists of all the workspace members invited to it, and their projects.

<figure><img src="/files/tPzaRbJsUIAmZFlMRFrd" alt=""><figcaption><p>Workspace view</p></figcaption></figure>

### Creating a workspace

To create a workspace click the **Add workspace** button. Insert your unique namespace name and/or invite some members.

### Member roles

* **Owner** - Creator of the workspace. The team owner can add/remove/edit/view projects and members of a team. Only the owner can delete the team.
* **Admin -** can add/remove/edit/view projects and members in a team (except for the owner).
* **Editor** -  can add and edit projects in your team.
* **Viewer** - can view projects in read-only mode, seeing only the **Graph** part of the schema.

### Inviting members

There are 2 ways of inviting members, both are in the **Edit Team** menu:

<figure><img src="/files/beqv8fYOsXweuHM2RWWE" alt=""><figcaption></figcaption></figure>

#### By email

Type in the email of the user you want to invite. It doesn't matter if they have a GraphQL Editor account. Simply click **Add member** and then set their role.

#### By magic link

Click **Magic links** in the **Edit Team** menu. Click **Create Magic Link,** set the allowed domain, expiration date and the role you want to assign the recipient. Then share it with them and as soon as they click it they will be on the team.

<figure><img src="/files/SCW7f0tpcHrInp2zRDwJ" alt=""><figcaption></figcaption></figure>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.graphqleditor.com/graphql-editor/readme/workspaces.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.