# Activity Tracking

Activity reports use a custom duration (how far back to track), a requirement (length on shift), and an option to include management to summarize all staff activity within the time period. This includes shifts, moderations, and leave of absences.

## <mark style="color:blue;">Activity View</mark> <a href="#view" id="view"></a>

The `/activity view` command allows you to view the activity of your staff members with one command.

**The Parameters**

**Duration**\
How far back we should grab data from.

**Requirement**\
How much time a user should have on duty to be considered 'active'.

**Include Management**\
Whether management should be included within your activity check.

**Shift Type \[Optional]**\
The shift type that you would like to view data for. The default is all.

## <mark style="color:blue;">Activity Auto</mark> <a href="#auto" id="auto"></a>

Activity auto allows you to send an embed at a specified interval to your desired channel which will display the same information as the `/activity view` command.

<figure><img src="/files/OsOAoAM9zznxfNREv0Bo" alt=""><figcaption></figcaption></figure>

The options here are the same as in activity view except for the frequency, which is how often the message should be sent.


---

# 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:

```
GET https://docs.trident.bot/modules/activity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.