> For the complete documentation index, see [llms.txt](https://docs.atlas.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atlas.design/atlas-ai-studio-overview/release-notes/release-0.19.0.md).

# Release 0.19.0

**NOTE**\
This release note includes only Workspace-related changes introduced in v0.19.0.

**Release Date:** April 2026\
**Previous Version:** v0.18.0 (March 2026)

**Updates:** Shared Workspaces, Collaboration, and Billing Controls

***

### 1. Shared Workspaces <a href="#id-1.-shared-workspaces" id="id-1.-shared-workspaces"></a>

**Shared Workspaces** — Introduced a new workspace system that enables teams to collaborate within a shared environment.

<figure><img src="/files/iL24iiqVojmxeJRs2oQK" alt="" width="455"><figcaption></figcaption></figure>

* Users can create dedicated workspaces and invite members via email

<figure><img src="/files/NT3brM87AIyr3jFHhk0B" alt="" width="546"><figcaption></figcaption></figure>

<figure><img src="/files/fMoTiWpZDtyiYZCsKP6c" alt="" width="563"><figcaption></figcaption></figure>

* Invited users are automatically added upon accepting the invitation link
* All members can access and work on projects within the same workspace

**Real-Time Collaboration** — Multiple users can work simultaneously on projects within a shared workspace environment (but it’s still experimental)

***

### 2. Roles & Permissions <a href="#id-2.-roles-and-permissions" id="id-2.-roles-and-permissions"></a>

**Workspace Roles** — Workspace owners can assign and manage different permission levels:

* **Admin** — Full control over the workspace, including:
  * Managing members
  * Editing workspace name
  * Setting billing and usage limits
* **Member** — Standard access to workspace projects without billing visibility

<figure><img src="/files/cZzdRRYlN3B71VF92WBc" alt="" width="512"><figcaption></figcaption></figure>

***

### 3. Billing & Usage Management <a href="#id-3.-billing-and-usage-management" id="id-3.-billing-and-usage-management"></a>

**Workspace Credit Limits** — Introduced flexible credit control mechanisms to manage usage:

* Limits define how many credits a workspace can spend within a billing period
* When the limit is reached, execution is blocked until the next usage period

**Usage Period Definition** —

* Usage is tracked in **rolling 30-day windows (UTC)**
* At the end of each period:
  * Per-member credit usage resets
  * Limits are reapplied for the new period

***

### 4. Limit Configuration Options <a href="#id-4.-limit-configuration-options" id="id-4.-limit-configuration-options"></a>

**Workspace-Wide Limits** —

* Apply to all members by default
* Define a global credit cap for the entire workspace

**Per-Member Limits** —

* Can override workspace-wide limits for specific users
* Allows granular control of individual usage

<figure><img src="/files/vHzfpElKkFP9qRNO2Vhc" alt="" width="563"><figcaption></figcaption></figure>

***

### 5. Shared Resources <a href="#id-5.-shared-resources" id="id-5.-shared-resources"></a>

**Shared API Access** — Exported workflow APIs are now visible and accessible within the shared workspace, enabling team-wide integration and reuse.

<figure><img src="/files/bfcABoVXQDg9CiKXvGHG" alt="" width="563"><figcaption></figcaption></figure>

***

### 6. Notes <a href="#id-6.-notes" id="id-6.-notes"></a>

This release introduces the foundation for **team-based collaboration in Atlas Studio** through Shared Workspaces, including role management, billing controls, and shared resource access. Other feature updates are not included in this note.


---

# 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://docs.atlas.design/atlas-ai-studio-overview/release-notes/release-0.19.0.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.