> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/facilitation/facilitator-dashboard/injects-grid.md).
# Injects Grid
The Injects Grid allows you to **jump to a specific inject in the MEL**. This is helpful if you're concerned that your players might miss an inject.
It can also be used alongside smartwords. For instance, if you provide an update using smartwords during the exercise, you can resend the inject, and it will be re-published with the updated smartword.
| Benefit | Feature |
| --------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Allows flexibility to send specific injects in the MEL at any point during the exercise |
Select up to 64 injects
Injects presented on an easy to navigate grid
Reorganise your inject grid live in Edit mode
|
## Running
When you click on an inject grid button this will jump to that inject in the MEL.
### Edit mode
To customise the position of your buttons, select edit mode and reorganise them by dragging and dropping them.
---
# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/facilitation/facilitator-dashboard/injects-grid.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.
