> 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/subscriptions-administration.md).

# Subscriptions

Manage the user subscriptions to all your organization’s favorites and dashboards.

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

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

{% hint style="success" %}
Related pages: [Favorites (Administration)](/administration/favorites-administration.md) and [Dashboards (Administration)](/administration/dashboards-administration.md)
{% endhint %}

The process of managing user [subscriptions](/basics/getting-started/subscriptions.md) is the same for favorites and dashboards, although you start from different locations.

## View the users who are subscribed to a favorite or dashboard <a href="#managesubscriptions-attheadministrationlevel-viewtheuserswhoaresubscribedtoafavoriteordashboard" id="managesubscriptions-attheadministrationlevel-viewtheuserswhoaresubscribedtoafavoriteordashboard"></a>

Click **Administration** > **Favorites** or **Administration** > **Dashboards** as applicable, then select the row of the favorite/dashboard and click **Subscribe**.

The **Subscribe** window contains a list of all users who can currently access the favorite\*. Users who already have an active subscription are identified by the darker envelope icon.

<div align="left"><figure><img src="https://content.gitbook.com/content/vQCmtGTR7MsjcI62Vdki/blobs/ANK1UJJtE12APshXJmCq/3124528362.png" alt="" width="228"><figcaption></figcaption></figure></div>

\*If users cannot access the favorite/dashboard, they cannot be subscribed to it. Users also need permission to subscribe.

## Subscribe a user to a favorite or dashboard <a href="#managesubscriptions-attheadministrationlevel-subscribeausertoafavoriteordashboard" id="managesubscriptions-attheadministrationlevel-subscribeausertoafavoriteordashboard"></a>

In the favorite/dashboard **Subscribe** window, click the user’s name, then select the required subscription settings and click **Subscribe**.

Subscriptions are sent at the time specified in the user's timezone, as calculated at the time of saving the item or each time the subscription is sent.

See [Subscribe to a favorite](/basics/getting-started/subscriptions.md#subscribe-to-a-favorite) for more information on the subscription settings.

## Edit a user’s subscription settings <a href="#managesubscriptions-attheadministrationlevel-editauserssubscriptionsettings" id="managesubscriptions-attheadministrationlevel-editauserssubscriptionsettings"></a>

In the favorite/dashboard **Subscribe** window, click the user’s name, then edit the subscription settings and click **Subscribe**.

## Unsubscribe a user from a favorite or dashboard <a href="#managesubscriptions-attheadministrationlevel-unsubscribeauserfromafavoriteordashboard" id="managesubscriptions-attheadministrationlevel-unsubscribeauserfromafavoriteordashboard"></a>

In the favorite/dashboard **Subscribe** window, click the user’s name, then click **Remove**.&#x20;


---

# 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/subscriptions-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.