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

# Favorites

Manage all the favorites in your organization’s Phocas site.

{% hint style="info" %}
User permission: Administration > Favorites
{% endhint %}

{% embed url="<https://phocassoftware.wistia.com/medias/88bj4pshow>" %}
Manage favorites, dashboards and subscriptions
{% endembed %}

{% hint style="success" %}
Related page: [Subscriptions (Administration)](/administration/subscriptions-administration.md)
{% endhint %}

[Favorites](/basics/favorites/view-and-save-favorites.md) can be saved by users when they want quick access to particular grid views or charts. As an administrator, you can manage all of those favorites.

Click **Administration** > **Favorites**. The **Favorites** page displays a list of all your favorites, including those you saved and those that were saved by other users. You can see details such as the database and folder in which the favorite was saved, and the user who saved it (owner). You can also see the last time the favorite was opened, which is useful when deciding if it can be deleted. You can filter the list by **Database**, **Folder** or **Owner**, or search for a specific favorite.

<figure><img src="https://content.gitbook.com/content/vQCmtGTR7MsjcI62Vdki/blobs/I6AhbPxDynL104ab6grE/3231449302.png" alt="" width="795"><figcaption></figcaption></figure>

## Share a favorite <a href="#favorites-administration-shareafavorite" id="favorites-administration-shareafavorite"></a>

On the **Favorites** page, select the row of the favorite > click **Share** > select the required sharing options > click **Save**.

For more information on sharing favorites in general, see [Share a favorite](/basics/favorites/view-and-save-favorites.md). For information on managing an individual user's favorites, see the [user account page](/administration/users/add-update-user/user-account-page.md) > **Favorites** tab.&#x20;

## Delete a favorite  <a href="#favorites-administration-deleteafavorite" id="favorites-administration-deleteafavorite"></a>

You can permanently a favorite if it is no longer required. This action cannot be undone. You can delete multiple favorites at the same time (left-click and drag to select the required rows).

On the **Favorites** page, select the row of the favorite > click **Delete** > **Yes**.

## Allow users to share favorites <a href="#favorites-administration-allowuserstosharefavorites" id="favorites-administration-allowuserstosharefavorites"></a>

You can control whether users can share favorites. See User permissions > [Collaboration](/administration/users/add-update-user/user-permissions.md#collaboration-sharing-permissions-for-dashboards-and-favorites).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.phocassoftware.com/administration/favorites-administration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.