> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-package-manager/user-and-console-guide/my-library.md).

# My Library

<div data-with-frame="true"><figure><img src="/files/7fQIodlAC3t21qKQAHZY" alt=""><figcaption></figcaption></figure></div>

***

## Core Functionality

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-album-collection">:album-collection:</i></td><td><strong>Manage My Library</strong></td><td>Take quick actions across published and shared packages.</td><td><a href="#manage-my-library">#manage-my-library</a></td></tr><tr><td><i class="fa-upload">:upload:</i></td><td><strong>Publish a Package</strong></td><td>Upload a new package to the CPM Registry</td><td><a href="#publish-a-package">#publish-a-package</a></td></tr><tr><td><i class="fa-clipboard-clock">:clipboard-clock:</i></td><td><strong>Publish a New Package Version</strong></td><td>Upload a new version of a package.</td><td><a href="#publish-a-new-package-version">#publish-a-new-package-version</a></td></tr><tr><td><i class="fa-lock-keyhole-open">:lock-keyhole-open:</i></td><td><strong>Manage Access Requests</strong></td><td>Accept or deny access requests.</td><td><a href="#manage-access-requests">#manage-access-requests</a></td></tr><tr><td><i class="fa-trash-can-slash">:trash-can-slash:</i></td><td><strong>Delete a Package</strong></td><td>Remove a package from your library.</td><td><a href="#delete-a-package">#delete-a-package</a></td></tr></tbody></table>

***

## **Manage My Library**

<div data-with-frame="true"><figure><img src="/files/7fQIodlAC3t21qKQAHZY" alt=""><figcaption></figcaption></figure></div>

My Library enables a user to manage his package catalogue. It organises packages into three distinct tabs:

* **Published**: This tab lists all packages the currently logged-in user has published.
* **Shared With Me**: This tab shows packages from other publishers that the current user has been granted access to.
* **Starred**: This tab displays all packages the user has marked as favourites and subscribed to for updates.

Across the tabs, each package provides quick access to the corresponding package management actions such as deleting, versioning, and downloading.

On the Published and Starred tabs, three toggle buttons — View All, Public, and Private — allow the user to filter the displayed packages by their access type.

## Publish a Package

<div data-with-frame="true"><figure><img src="/files/OghaYw6oEMjtvjjy8mRI" alt=""><figcaption></figcaption></figure></div>

Triggered by the **Publish Package** button on the Published tab. The user must fill out the following fields when publishing a new package:

* **Package name** *(required)* — the unique name for the new package.
* **Description** *(required)* — a free-text description.
* **Artifact Hosting Mode** *(required):* The user has 2 options to host a packages' DAR files
  * **Upload DAR to CPM:** the file is hosted by CatalyX Package Manager.
    * For publishing private packages, only the "upload DAR to CPM" option is available.
  * **Provide External Artifactory Link:** the file is hosted by the user and must provide an external artifactory link. When choosing this option, the user also has the option to provide:
    * **Documentation link**: optional link to corresponding docs
    * **Web-based URL**: optional link to a website corresponding to the application
* **Access Model** *(required):* the user has 2 access options for his packages:
  * **Public:** any registered user can download the package
  * **Private:** a user must request and recieve access to the package to download it
* **Version** *(required)* — a version string (e.g., `0.1.12`).
* **Tags** — a comma-separated list of tags.

## Publish a new Package Version

<div data-with-frame="true"><figure><img src="/files/7Bxp21iPfAie5A4CEKlX" alt=""><figcaption></figcaption></figure></div>

Triggered by the **Create New Version** icon for a package in the Published tab, a user can publish a new package version. The form is pre-populated with the package's existing name and access mode, and allows the user to update the other fields accordingly.

## Manage Access Requests

<div data-with-frame="true"><figure><img src="/files/JilQMTDCfO68ZHlwgwk8" alt=""><figcaption></figcaption></figure></div>

Accessed via the **Manage Access Requests** button on the Published tab, a publisher can manage all incoming access requests for private packages: accept, deny, or revoke access to a package.\
\
When an access request is approved, the requesting user receives an update notification and will be able to download the package.

## Delete a Package

To delete a package, simplify click the **Trash** icon on a package instance on the **Published** tab.

***


---

# 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:

```
GET https://docs.catalyx.solutions/catalyx-package-manager/user-and-console-guide/my-library.md?ask=<question>
```

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.