> 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/basics/getting-started/subscriptions.md).
# Subscriptions
Stay on top of important changes by subscribing to favorites, dashboards, and alerts and receiving email notifications when they update.
A subscription sends information from Phocas to your email address according to the delivery settings you choose. Subscription emails are sent to the email address in your account settings.
Subscriptions are personal. Sharing an item with someone doesn't automatically subscribe them to it.
The **Subscriptions** tab on your homepage lets you view and manage all your subscriptions in one place. Click a subscription item to open it.
What you can subscribe to and the available subscription settings depend on the Phocas product or feature you're using.
Related pages:
* [Analytics > Manage subscriptions](/analytics/manage-subscriptions.md) to learn how to subscribe to Analytics and Financial Statements favorites, alerts, and dashboards.
* [Flex Modes > Manage subscriptions](/flex-modes/save-and-share-your-work/manage-subscriptions.md) to learn how to subscribe to Flex Mode favorites and alerts
---
# 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/basics/getting-started/subscriptions.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.
