> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/binders/global-and-local-definition-lists.md).
# Global and local definition lists
In traditional documents, you can insert a definition list as a separate clause by automatically generating it using the document toolbar.
However, such functionality is often not enough:
* In binders, you may run into the situation of having certain defined terms in one document and other defined terms in another.
* In some jurisdictions, it is customary to have “local” definition lists containing only those terms that are present in a specific clause.
Clause9 allows this kind of flexibility: for each definition list, you can define the scope and interactions with any other definitions lists present in the document/binder. To tweak these options, you should simply select the definition list, and visit the Advanced menu at the right side of your screen.
These eight (!) different options should allow you sufficient flexibility to meet all your definition needs!
---
# 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://help.clause9.com/binders/global-and-local-definition-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.
