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

# Workspaces

A **Workspace** is an operational domain inside your organization. It groups people, repositories, and connected resources for a specific team, product, or environment.

## How workspaces relate to the gateway

The Cloud and AI Gateway is an abstraction layer, and in practice your organization is usually structured into **multiple workspaces**. Each workspace can contain repositories, and those repositories attach cloud storage and AI/LLM resources.

## What you can do in Workspace management

* list all workspaces you can access,
* create a new workspace,
* edit workspace metadata/configuration,
* remove a workspace,
* manage workspace-level rights (read/write/admin, depending on role).

## Recommended structure patterns

* Split by environment: `dev`, `staging`, `prod`
* Split by business domain: `search`, `assistant`, `analytics`
* Split by security boundary: regulated vs non-regulated workloads

## Why this matters

Good workspace design improves:

* security isolation,
* policy clarity,
* cost attribution,
* and observability granularity.

## API mapping

* `POST /workspace`
* `GET /workspace`
* `GET /workspace/{id}`
* `PUT /workspace/{id}`
* `DELETE /workspace/{id}`

See: [Workspace API](/support-reference/platform-api-reference/workspace.md)


---

# 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.flashback.tech/flashgate-platform/organization/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.