> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/v.8-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/v.8-documentation/user-guide/improving-shop/managing-modules/modules-and-services.md).

# Modules and Services

In PrestaShop 1.7 the Modules and Services page is divided into three tabs to help you perform easily what you want to do regarding your modules:

* Selection: this is where you can discover and install new modules to improve your store when you’re beginning or growing with PrestaShop,
* Installed Modules: where you can manage your modules on a daily basis,
* Notifications: review modules notifications, when you need to take action (updates or configuration) to guarantee the good functioning of your modules.

At the top of the page, you will also find two important features: the connection to Addons and the "Upload a module" option.

Follow the links for more details on these tabs:

* [ Modules Selection](/v.8-documentation/user-guide/improving-shop/managing-modules/modules-and-services/modules-selection.md)
* [ Installed modules](/v.8-documentation/user-guide/improving-shop/managing-modules/modules-and-services/installed-modules.md)
* [ Module notifications](/v.8-documentation/user-guide/improving-shop/managing-modules/modules-and-services/module-notifications.md)


---

# 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/v.8-documentation/user-guide/improving-shop/managing-modules/modules-and-services.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.