> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/tutorials/introductory-presentation/adding-other-ifx/adding-the-engage-link-map.md).
# Adding the ENGAGE LINK map
For this example, we will add the ENGAGE LINK map IFX.
1. Move the playhead to approximately `00:05:03`.
{% hint style="info" %}
This is the point when the third recording finishes introducing the concept of IFX. To ensure that the playhead is at the correct time, you can move it to the start of the third recording, press play, and then press pause after the recording’s audio stops.
{% endhint %}
2. From the left-hand side of the editor panel, select **IFX**.
3. In the search field, enter `link map`, and then select the search icon.
4. From the filtered list of IFX, select **Link Map**.
5. Place the IFX on the stage.
ENGAGE Link map on the stage
---
# 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.engagevr.io/engage/experience-editor/tutorials/introductory-presentation/adding-other-ifx/adding-the-engage-link-map.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.
