# Activity

## Introduction

Activity tracking lets users monitor actions taken, providing a clear view of next steps in the workflow. In a module, each activity represents a specific action on an entry, making tasks intuitive and easy to track.

## Functionality

Each activity entry logs a distinct action that must be performed, which can then be tracked and managed through the module. Examples of activities within a module could include actions like **Submit**, **Approve**, **Reject**, and **Process**. These activities are defined based on the specific needs of the workflow or business process.

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

## **Activity Naming**

Activities are typically described using active verbs to represent the action being performed. For example:

* **Submit** (initiating the action)
* **Approve** (confirming or approving a request)
* **Reject** (declining a request)
* **Process** (carrying out the necessary processing steps)

These activities are displayed as interactive buttons within the software, enabling users to execute the required tasks.

## **Roles and Permissions**

Different roles may be assigned to specific activities based on their responsibilities within the workflow. For instance:

* **Approve** and **Reject** activities may be designated to the **Manager** role.
* **Process** could be assigned to the **Human Resource** department, or other relevant teams depending on the task at hand.

By leveraging the activity feature, users can efficiently track and manage their tasks within any given module. The ability to define, assign, and track activities ensures clarity in workflows and supports smooth execution of business processes.


---

# Agent Instructions: 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://inistate.gitbook.io/home/features/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.