> 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/powershell-universal/platform/notifications.md). # Notifications View PowerShell Universal notifications for configuration errors and system events, filtered by Information, Warning, and Error severity levels. PowerShell Universal can generate notifications for numerous reasons. These can include operations such as restarting a dashboard or a configuration error. Notifications are available under **Observe > Notifications** or by clicking the bell icon within the admin console. You will be redirected to the notifications page with a list of the unread notifications. ## Levels Notifications can be Information, Warning or Error levels. When an error level notification is generated, the bell icon will change to an exclamation mark and change to red. You can configure which levels are generated under **Settings gear > General**. Change the Notification Level setting to the lowest level you'd like to see. For example, if you set it to Warning, you will only see Warning and Error notifications. --- # 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/powershell-universal/platform/notifications.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.