> 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/pim3/fundamental-concepts/global-lists.md).
# Global lists
Global lists is a key element of Struct PIM and one of the building blocks that enable the definition of any data model
### What are global lists
Global lists are used to create predefined lists of entities that can be referenced on products, variants, categories or even other global lists.
The data model of a Global list is defined by an underlying attribute. By using Complex attributes, values in a global list can become entities themselves which has a number of data fields. Global list values can even be configured to reference other global list values by using a GlobalListValue attribute within the definition of a global list.
{% hint style="info" %}
**Example:** A list of brands is defined by a global list, so a brand can be selected on products in the system. Each brand has a name, a localized description and a logo. These 3 data fields are all defined on the global list and maintained here. On the product structure an attribute is attached that is configured to allow selection of 1 entity from the global list of brands.
{% endhint %}
---
# 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/pim3/fundamental-concepts/global-lists.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.