> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/6.0.3/admin-guide/settings/customization/advanced-concept-settings.md).
# Advanced concept settings
In order to turn on the ability to store relations of certain links throughout the application `Store relation information in document` needs to be turned on.
By activating this a depth counter will appear. This alters the depth of the requests thats being made in order to get relation information. By itself it will only get the information about relations, but in order to actually store the information we need to turn on the storing on each specific tag type we want to store information for. [See appendDataToLink here ](/newsroom-planner/6.0.3/admin-guide/settings/customization/loadable-components/tags.md#configuration-keys)
**Example**:
Imaging following concept hierarchy
`Paris` > `France` > `Europe` > `Earth` > `Milky Way`
If I was about to add `Paris` as a concept to an item with store relation activated it would also fetch information about its parents until chosen depth.
Following the image above my item would then receive information about `Paris` and as children under the concept, links pointing to `France`, `Europe` and `Earth` would also appear because of the depth of 3.
```xml
```
---
# 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.navigaglobal.com/newsroom-planner/6.0.3/admin-guide/settings/customization/advanced-concept-settings.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.