> 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/catalog-manager/catalog-manager-overview.md).

# Catalog Manager Overview

The **Catalog Manager** is where the work you build inside Astera Studio becomes available to the rest of your organization. A workspace is private by default — only you can see what is in it. When you are ready to share dashboards, dataprep recipes, AI skills, and other artifacts with teammates, you **publish** your workspace as a **catalog**. The Catalog Manager is the surface where every published catalog and every item inside it lives.

### What a Catalog Is

A catalog is a named, published snapshot of a workspace. When you publish from a workspace, Astera Studio bundles every shareable artifact in that workspace — dataflows, dashboards, AI skills, dataprep recipes, connections — into a single catalog with a name you choose. Everyone in your organization who has the right role can browse, search, and consume items from that catalog.

* **One workspace → one catalog.** Publishing from a workspace creates or updates a catalog of the same name. To share a different bundle, publish from a different workspace.
* **Catalogs hold many artifact types**. A single catalog can contain dataflows, dashboards, recipes, skills, reports, and connections — whatever was in the source workspace.
* **Catalogs version on every publish**. Each time you publish with the same name, Astera Studio overwrites the existing version so end users always use the latest one.
* **Catalogs are governed by roles**. Access is granted at the role level, with four access levels (*Use*, *Read*, *Write*, *No access*).

{% hint style="info" %}
**Important:** Catalog ≠ Workspace. Your workspace stays editable; the catalog is the shared snapshot. Editing an artifact in the workspace does not affect the published catalog until you publish again. This separation lets you iterate in private and release deliberately.
{% endhint %}

### Overview 

When you open the Catalog Manager, you land on the Overview screen. 

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

This is the top-level view of every catalog published in your organization's tenant. It gives you a summary of what has been shared, how many artifacts exist across all catalogs, and a breakdown of what types of assets are available.

**System Catalogs:** These are artifact bundles published and maintained by Astera that are available in your workspace by default. If a newer version is released, you can click the update button to update to the latest version.

### Access&#x20;

Opens the Access management screen where you can review and edit role-based permissions for each catalog.&#x20;

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

### Catalogs

The left panel lists every catalog published in the tenant. In the example above, four catalogs are shown. &#x20;

Click any catalog name to open that catalog and browse its contents. The Overview and Access navigation items above the catalog list apply to the tenant as a whole, not to any individual catalog.

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


---

# 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/catalog-manager/catalog-manager-overview.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.