# Organizations and Workspaces
### Organization
An **Organization** is the top-level container for your account.
* When you sign up, you get your **own Organization** by default.
* This ensures **data isolation** so your work stays separated from other users and organizations.
***
### Workspace
A **Workspace** is an **isolated space** where your testing data lives, including:
* test executions (runs)
* reports and results
* execution history
* run artifacts (like videos, where supported)
Workspaces help you keep testing data organized across different apps, environments, or teams.
***
### Default starter workspace
When you sign up, ratl.ai Studio automatically creates a **starter workspace** for you so you can begin running tests immediately.
You can continue using it, or create additional workspaces as needed.
***
### Creating a workspace
You can create a workspace from either of these places:
#### Option 1: From Settings
1. Open **Settings**
2. Go to the **Workspaces** section
3. Click the **Add New** button
4. Enter a workspace name (follow naming rules below)
5. Create the workspace and switch to the new workspace if needed\
\
  \
\ 
#### Option 2: From the Sidebar
1. Open the **Sidebar**
2. Find the **Workspace** section / switcher at the top of the sidebar below the logo
3. Click on it to expand the dropdown
4. Click **Create Workspace**
5. Enter a workspace name (follow naming rules below)
6. Create the workspace and switch to the new workspace if needed
***
### Workspace naming rules
Workspace names must follow these rules:
#### 1) Workspace name must be unique
Your workspace name must be **unique**.
If your preferred name is taken, add a clear suffix like:
* `myapp-staging`
* `myapp-qa`
* `myapp-2026`
#### 2) No special characters
Workspace names must **not** contain special characters like:
* `@` `#` `$`
To keep naming predictable, avoid symbols in general.
#### 3) Only hyphens are allowed as separators
If your workspace name has multiple words, use **hyphens (`-`)**.
✅ Valid examples:
* `acme-web`
* `acme-checkout`
* `web-tests-staging`
* `ratl-studio-demo`
❌ Invalid examples:
* `acme@web`
* `acme#checkout`
* `acme$prod`
* `acme_web`
***
### Recommended workspace structure
To keep things clean as your execution history grows, most teams create workspaces by:
#### By environment
* `myapp-dev`
* `myapp-staging`
* `myapp-prod`
#### By product area
* `myapp-auth`
* `myapp-checkout`
* `myapp-search`
Choose a pattern early and stay consistent — workspace naming becomes hard to clean up once lots of runs are stored.
***
#### Where can I access my workspaces?
You can always find workspaces from:
* **Settings → Workspaces**
* the **Sidebar workspace switcher**
***
### Summary
* Your account includes an **Organization** to keep data isolated.
* A **Workspace** is an isolated space where your test execution data is stored.
* A **starter workspace is created automatically** when you sign up.
* You can create new workspaces from **Settings** or the **Sidebar**.
* Workspace names must be **unique**, contain **no special characters**, and use **hyphens only**.
---
# Agent Instructions: 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:
```
GET https://docs.ratl.ai/guide/manage-account/organizations-and-workspaces.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.