> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/1.7-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/1.7-documentation/user-guide/improving-shop/managing-modules/modules-and-services/module-notifications.md).

# Module notifications

It is important to keep your modules up-to-date, whether some setting is missing or a new version is available. This page helps you review the actions you need to perform on concerned modules.

Modules to configure

You will at times get notifications from installed modules. Most of the time, the notification help you complete the configuration of modules that are installed but are not yet ready to be used: updating their settings should make the notification disappear... and your module work properly.

## Modules to update <a href="#modulenotifications-modulestoupdate" id="modulenotifications-modulestoupdate"></a>

When one of your modules has an update available on the Addons site, PrestaShop will let you know about it, and an "Update" button will appear. Click on this button to update your modules. Before updating your module, you can have a look at its changelog to review what's new with this new version. It is useful to check your modules after the update: are these new features working properly?


---

# 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.prestashop-project.org/1.7-documentation/user-guide/improving-shop/managing-modules/modules-and-services/module-notifications.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.