> For the complete documentation index, see [llms.txt](https://guide.mymodone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mymodone.com/how-do-i.../use-the-dashboard/engagement-by-location.md).
# Engagement By Location
This tile provides an overview of Team Member engagement by Location.
Engagement By Location Tile
Each bar indicates 30-day performance, and the line indicates 90-day performance. Five locations are shown at a time. If more than five locations are available to display, arrows will appear at the top of the chart. To advance forward or backward, click the appropriate arrow.
Note that engagement is a combination of responding to content and, if applicable, attendance logging.
Hover over any location bar for the 30-day versus 90-day results and trend. Click a location bar to view detailed Team Member statistics.
Location Engagement - Team Member Detail
The Team Member detail includes 3 tabs: 1) Team Lead Engagement, Team Member Engagement, and Attendance. Click a tab to activate the view.
Each view displays an alphabetical list of Team Members. For each Team Member, the 30-day versus 90-day trend is displayed along with their performance during each timeframe.
This drill-down quickly shows those Locations and Team members who are engaging with the Platform and those who are not.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://guide.mymodone.com/how-do-i.../use-the-dashboard/engagement-by-location.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
