> 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 Find out where to manage your own subscriptions and subscriptions for other users A subscription sends information from Phocas by email according to the selected delivery settings. Sharing an item with someone doesn't automatically subscribe them to it. Where you manage a subscription depends on the item type and whether you're managing it for yourself or another user. ### Manage subscriptions for other users See [Favorites and alerts](/administration/favorites-administration.md#manage-favorite-and-alert-subscriptions) for Classic favorites and alerts. Dashboard subscription administration is currently unavailable. ### Manage your own subscriptions See these pages: * Classic favorites, alerts, and dashboards: [Manage subscriptions](/analytics-classic/manage-subscriptions.md) * Analytics favorites and alerts: [Manage subscriptions](/analytics/save-and-share-your-work/manage-subscriptions.md) * Dashboards: [Subscribe to a dashboard](/basics/dashboards/use-dashboards.md#subscribe-to-a-dashboard) --- # 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=&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.