> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/reference/settings/integration/apps/apps-details/extension-points/extension-point-types.md).
# Extension point types
The selection of extension points available inside the PIM.
Extension point types define where the app will be shown inside the PIM. You can setup multiple extension points, but they can only have one extension point type.
| Extension point | Description |
| :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: | ---------------------------------------------------------------------------------------- |
| 
| Adds a page to the top bar menu for the custom app. |
| 
| Adds a widget that can be integrated into the dashboard. |
| 
| Adds a tab that can be added to any data model in the product structure setup. |
| 
| Adds a new section that can be added to any data model in the product structure setup. |
| 
| Adds a new property which can be added to any data model in the product structure setup. |
| 
| Adds a new exporter type that can be used when exporting data from the PIM. |
| 
| Adds a new search action to search results actions. |
| 
| Adds a widget that will be displayed in the sidebar. |
---
# 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.struct.com/reference/settings/integration/apps/apps-details/extension-points/extension-point-types.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.