> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/ph-v1.7/design/architecture/low-level-design/services/update-and-approve-attendance.md).

# Update & Approve Attendance

## Overview

The **Proximity Supervisor Flow** for managing attendance registers is designed to provide supervisors with a seamless experience for selecting projects, viewing associated attendance records, and managing the details effectively. The flow emphasises ease of navigation, quick access to project and register information, and actionable steps to edit or approve attendance records.

## **Features**

* **Project Selection**: Enables supervisors to pick a specific project to manage.
* **Registers Inbox**: Displays filtered attendance registers for selected boundaries.
* **View Attendance**: Provides detailed attendance information for campaigns and projects.
* **Edit Attendance**: Allows supervisors to update attendee records.
* **Approve Attendance**: Facilitates approval with clear validation and comment requirements.

<table><thead><tr><th width="262">Role</th><th>Description</th></tr></thead><tbody><tr><td>PROXIMITY_SUPERVISOR</td><td>manage attendance registers, approving and editing the attendance data</td></tr></tbody></table>

Each step in this flow ensures user-friendly interactions and adheres to the necessary validation rules and role-based permissions for supervisors and project managers.

{% hint style="info" %}
*<mark style="color:red;">**Note:**</mark>* *In Payments version 0.1, each user will be associated with only one project.*
{% endhint %}

## **Sequence Diagram**

<figure><img src="https://content.gitbook.com/content/ugLvZh3s3IGcc8JYqNN7/blobs/GPIiuoDhyJjRSQSP6p3w/image.png" alt=""><figcaption><p>Attendance Edit and Approval By Proximity Supervisor</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://docs.digit.org/health/ph-v1.7/design/architecture/low-level-design/services/update-and-approve-attendance.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.