> 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/common-features/team-member-portal/my-team-manager.md).

# My Team Manager

The My Team Manager helps Team Leaders monitor the engagement of Team Members within their location.

Click the My Team icon ( <img src="https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2Fz3AmwPLwGlkkjGoYayoK%2Fusers-solid%20(1).svg?alt=media&amp;token=9650e2b3-ecb0-4af1-b4c0-5d6664b87520" alt="" data-size="line"> ) in the Navigation Ribbon to launch the My Team Manager. My Team Manager includes two sections: Active Content Engagement and Historic Performance.

### Active Content Engagement

If active content exists (i.e., the call to action has not yet expired) that requires a Team Member response (either a call to action response or logging attendance),  it will appear in the Active Content Engagement section. This section is divided into two subsections: Alerts and Scheduled content.

For each active content, the title/subject, call to action date range, and the applicable summary level statistics are displayed. If a quiz is included, the quiz score will be underlined. Click to see the aggregate result for each quiz question. When visible in the Active Content Engagement banner, click the ![](https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FFnt9TEBqWHO6gK56GVak%2Fretweet-solid.svg?alt=media\&token=4f0c7b18-316a-475a-862e-8ba95c783399) icon to check for new content.

<figure><img src="https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FdYY4pZNyE1eedMuJG30F%2FActive%20Content%20Engagement%20v2.png?alt=media&amp;token=6e425622-7273-4e99-92d9-a4525102b6b2" alt=""><figcaption><p>Active Content View</p></figcaption></figure>

Click the ![](https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2Fz3AmwPLwGlkkjGoYayoK%2Fusers-solid%20\(1\).svg?alt=media\&token=9650e2b3-ecb0-4af1-b4c0-5d6664b87520) icon on any content row to see a list of the in-scope Team Members and their respective responses. To change the view, click the view dropdown and choose the desired view.&#x20;

Available choices are dependent upon the content options chosen and include:

* All Eligible (default view)
* Attendance: Not Logged
* Call to Action: Not Responded
* Out of Office

<figure><img src="https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FcC2PLRfLr6ntOLc85y1v%2FScheduled%20Content%20v2.png?alt=media&amp;token=684342d5-3838-4bbf-a272-02aa99daba98" alt=""><figcaption><p>Team Member Detail</p></figcaption></figure>

#### Create Out of Office Request

If a Team Member is out of the office and unable to interact with the content, an out of office request can be created for review and approval by the modONE Administrator.

To create an out of office request:

1. Click the ![](https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2Ffv77QPyCKkFQ7Z7TUbhG%2Fcalendar-xmark-regular.svg?alt=media\&token=49105221-e201-4e21-8c71-76a19d9c9d8c) icon beside the Team Member who is out of the office to activate the out of office status request pop up
2. Click the out of office reason dropdown and choose a reason
3. Type a comment in the comment box. This is optional for all reasons except "Other"
4. Click the "Save" button to create the request

<figure><img src="https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2F1cZOhhcRC6i3PjEcmJvq%2FSet%20OO%20Status%20v2.png?alt=media&amp;token=957b13a0-f719-40ed-a0c1-5f72f7da471d" alt="" width="375"><figcaption><p>Out of Office Status Request</p></figcaption></figure>

Once the request is created, a rotating hourglass icon (![](https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FCl966f1tTyH7sL1yLtGf%2Fhourglass-half-regular.svg?alt=media\&token=33837edb-e3a7-4634-91d3-6f6ac5910e8b)) will appear, indicating that the request is awaiting approval.

#### Remove Pending Out of Office Request

To remove a pending out of office request:

1. Click the ![](https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FCl966f1tTyH7sL1yLtGf%2Fhourglass-half-regular.svg?alt=media\&token=33837edb-e3a7-4634-91d3-6f6ac5910e8b) icon beside the Team Member with a pending out of office request
2. Click the "Yes" button to confirm the removal of the request

<figure><img src="https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FXjkQ0QJ79deic99FIdYG%2FRemove%20OOO%20Request%20v2.png?alt=media&amp;token=2a2e8c0f-1f9c-40a3-bfcf-638b20e6a314" alt="" width="375"><figcaption><p>Remove Out of Office Status Request</p></figcaption></figure>

#### Approved Out of Office Request

Once an out of office request is approved, the rotating hourglass icon will be replaced by a red ![](https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2F4Tpdy4HLmGV1QNWOk131%2Fxmark-solid.svg?alt=media\&token=3ed6277e-6ae1-4e84-b8af-da972e054dea) icon.

### Historic Performance

The Historical Performance section summarizes Team Members' historical engagement and comprehension during the selected timeframe.

To select a specific timeframe for reviewing team members' historical performance, utilize the dropdown box labeled "Timeframe." This feature allows for a customizable overview, enabling you to analyze engagement and comprehension from various periods.

If a comprehension quiz was included with the content, the quiz average will be underlined. Click this number to see an overview of how the Team collectively scored on each question.

Click the ![](https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2Fz3AmwPLwGlkkjGoYayoK%2Fusers-solid%20\(1\).svg?alt=media\&token=9650e2b3-ecb0-4af1-b4c0-5d6664b87520) icon on any content row to see a list of the in-scope Team Members and their respective responses. Similar to the summary view, if a quiz was included with the content, the Team Member's quiz score will be underlined. Click this number to see the Team Member's quiz responses.

<figure><img src="https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FHgaeVX7ElhlepnaScV6o%2FMy%20Team%20Historic%20DD%20v4.png?alt=media&amp;token=5729d0af-0ce0-4fc6-badd-5191a304dd27" alt=""><figcaption><p>Historic Performance Team Member Detail</p></figcaption></figure>

### Team Roster

To view a Team Roster, click the "Team Roster" button found on the right-hand side of the page.

{% hint style="info" %}
The Team Roster is especially helpful when Team Members need help signing in to modONE. This provides the Team Leader with the necessary information to assist.
{% endhint %}

<figure><img src="https://3373848439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVs9KFF5j76G7XSrhwbWT%2Fuploads%2FG8kHgnvO3kogWjHazDfA%2FTeam%20Roster%20vUpdated.png?alt=media&amp;token=efad215e-6f26-4122-b698-d3dcef94b54d" alt=""><figcaption><p>Team Roster</p></figcaption></figure>


---

# 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/common-features/team-member-portal/my-team-manager.md?ask=<question>&goal=<endgoal>
```

`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.
