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

# Workspace Setup

Create and manage unique AirOps environments

## What is a Workspace?

A Workspace is a unique AirOps environment. When you first sign up with AirOps, you are asked to pick a name for the Workspace. Any subsequent users you invite will be granted access to the same space for easy collaboration!

{% hint style="info" %}
If you do not belong to a paid workspace, you can create another workspace only while you belong to fewer than five active workspaces. Free and trial workspaces count toward this limit. Belonging to a paid workspace exempts you from this creation cap.
{% endhint %}

## How Do I Create a Workspace?

To get started, click on the double-arrow icon in the top-left corner of the page, next to the name of your current Workspace. From there, click the "Create Workspace" button and follow the prompt.

{% @arcade/embed url="<https://app.arcade.software/share/Pi22ZeZm3GdBgQPRcgjD>" flowId="Pi22ZeZm3GdBgQPRcgjD" %}

Once completed, that same double-arrow icon will allow you to navigate through each Workspace that you belong to.

## When should I create a new workspace?

Workspaces can be useful in a variety of scenarios. Some of the most common that we've seen include:

* Having separate "Dev" and "Production" environments for testing vs. deploying your Workflows
* Providing a Workspace for each team within your organization, e.g. a "Sales" workspace vs. "Marketing" vs. "Product"
* Personal sandboxes to avoid clutter on your company's main Workspace


---

# 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.airops.com/your-workspace/workspaces.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.