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

# Workspace UI Walkthrough

The Workspace Panel is divided into four areas:&#x20;

<img src="/files/PwIy1hePHBlZcMCuOXOZ" alt="" width="213">

* Header - Shows you the workspace name and gives you an option to **Switch workspace**.&#x20;
* Action buttons - **Upload** to add local files and **Publish Catalog** to share items in your workspace with the rest of your organization.&#x20;
* Item controls - An **All**-filter dropdown to narrow the list by category, an Add Item button to create new items, a refresh icon, and a search icon.&#x20;
* Item categories - Grouped sections that organize everything in your workspace, each showing a live item count.

### &#x20;Header

To switch between workspaces, click **Switch Workspace**. This opens the workspace selector panel, where you can switch to an existing workspace or create a new one.

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

### Action Buttons

#### **Upload**&#x20;

To upload any local files to your workspace. Astera Studio uploads the files in chunks. Progress is shown per file. Once finished, the files appear under Source Files and are immediately available for use in Studio.&#x20;

#### **Publish Catalog**&#x20;

Workspaces are private by default, only you can see what is in them. To share with the rest of your organization, you publish the entire workspace as a named catalog in one operation.

1. Click **Publish Catalog** button. It opens the publish modal.
2. In the Publish modal, accept the auto-populated catalog name or rename it to something more descriptive for consumers.&#x20;
3. Click **Publish Catalog** and wait for the four-phase flow (scan → preview → publish → success) to finish.
4. Once successfully published, all workspace items become accessible organization wide.&#x20;
5. Click **View in Catalog Manager** on the success screen to jump to the new catalog and set up role-based access.

### Item Controls

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

#### **Add Item**&#x20;

There is a list of things that you can add to your workspace:

* **AI Skills —** Instruction documents that define how an agent should behave, what it knows, and what rules it follows.
* **Connections —** Database, API, or connector integrations that give agents access to external systems and data sources.
* **Import —** Bring existing files and folders into your workspace.

### Item Categories&#x20;

A workspace organizes its contents into categories. Each category groups items of a specific type so they are easy to find and easy to share with the AI.&#x20;

<img src="/files/sLGn7bPJKWJsCnGeTap7" alt="" width="213">

The number to the right of each category is the live item count. Click on a category to expand it and see the items it contains.&#x20;

<figure><img src="/files/3RwhoipDLpCZQ1amuH8b" alt="" width="303"><figcaption></figcaption></figure>

Right clicking an item opens a small context menu with Copy Path and Delete.&#x20;

<img src="/files/Hw2YLbM9YfEvuzqinm9Z" alt="" height="180" width="360">

### &#x20;Disconnect from the Active Workspace&#x20;

1. Click on **Switch Workspace** to open the Workspace Selector panel.&#x20;
2. Locate the active workspace card. It is highlighted and shows a red Disconnect icon.&#x20;
3. Click the **Disconnect** icon.&#x20;

<img src="/files/KT4J97EKj9OIP2CLnO2h" alt="" height="318" width="538">


---

# 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://documentation.astera.com/astera-studio/workspace/workspace-ui-walkthrough.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.
