> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/web-interface/administration/configuration/notifications/subscriptions.md). # Subscriptions Create Subscriptions in Devolutions Server to define which activities, such as entries, users, or PAM events, trigger email notifications and to whom. The ***Subscriptions*** are intended to send email according to activities on Devolutions Server. It could be activities on entries, user accounts, system settings, etc. To create a ***Subscription***, click on the ***Add*** button. Then, fill in the informations in the following fields: ### Subscriptions
OptionDescription
NameDisplay name of the subscription.
SubscriberOne subscriber that will receive the notifications from the current subscription. A subscriber or a subscriber group can be selected.
Subscription category

Category of the subscription. Can be set to one of the following possibilities:

  • Entry
  • User
  • Vault
  • User groups
  • PAM privileged account
  • PAM provider
  • PAM checkout
  • PAM team folder
  • System settings
  • Administration log
  • Workspace log
  • Devolutions Gateway
  • PAM checkout policy
  • PAM OTP template
FiltersThe filters are tied to the subscription category and each of them has their own filters. You can add a filter with the Add Filter button. Be aware that the filters are cumulative.
--- # 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.devolutions.net/server/web-interface/administration/configuration/notifications/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.