> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/tasks/approval-activity.md).

# Approval tasks activity

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). Platforms: web, iOS and Android. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/tasks/approval-activity.md).
{% endhint %}

The history of approval requests on tasks: who asked for approval, approved or rejected which task, and when.

* **Where:** web: "Audit Trail" on the [feed](https://docs.snapfix.com/how-the-apps-work/screens/tasks/feed.md) or a [group's task list](https://docs.snapfix.com/how-the-apps-work/screens/tasks/group-tasks.md) while "Approval tasks only" is on (a dialog); iOS and Android: the approval activity button on the feed or a group's task list, shown while "Approval tasks only" is on
* **Who:** anyone who can open those lists. Which events show differs per platform (see [Platform differences](#platform-differences)).
* **Feature:** [Task approval](https://docs.snapfix.com/product/features/tasks/task-approval.md)

![Approval tasks activity](https://3653879137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVVGa79QbcEkJ7n8srxe%2Fuploads%2Fgit-blob-a36ff7f50ff358110d69e8d48ff130e62dee391b%2Fapproval-activity.png?alt=media)

## Layout

Top to bottom:

1. Title: web "Approval Tasks Activity" with a close button, hidden while loading. Escape and clicks outside never close the web dialog, so it can't be closed until the events load. iOS and Android: "Task Approval Activity" with back.
2. The events, oldest at the top and newest at the bottom; the screen opens scrolled to the newest. A divider per day: web "Today", "Yesterday", the weekday for the last week, then "DD/MM/YYYY"; iOS a similar label in capitals; Android the chat date format.
3. Each event shows an icon for the kind of event, the user's name in bold followed by "requested Task Approval", "approved a Task" or "rejected a Task", the task's title, the time ("HH:mm"), and the user's picture or initials. The web builds the bold name as HTML, and shows the name and the task's title in title case ("Leaking Tap In Room 101"). A deleted user's name starts with "Del -", because deleting an account puts "DEL -" before the first name.

Scrolling to the top loads older events: 20 at a time (web from the server, Android from the device). iOS loads every event at once from the device.

## Inputs

None. The web dialog takes the list's search and filters, except "Approval tasks only", from the screen that opened it.

## Actions

| Action                   | Who    | What happens                                                                                            | API                                                                                                                                      |
| ------------------------ | ------ | ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Load events (web, group) | anyone | Events of the group's completed tasks that match the list's search and filters.                         | [`POST /v1/app/tasks/statuses`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksstatuses)                     |
| Load events (web, feed)  | anyone | Events of the site's tasks that match the feed's search and filters. On a multi-site the request fails. | [`POST /v1/app/tasks/statuses-by-parent`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksstatuses-by-parent) |
| Load events (mobile)     | anyone | Read from the device database; nothing is sent.                                                         |                                                                                                                                          |
| Close or back            | anyone | Returns to the list. Events can't be opened.                                                            |                                                                                                                                          |

## States

* **Loading:** web: a spinner, and no close button; a spinner at the top while older events load. Android: the refresh spinner.
* **Empty:** web: "No activity logs found". iOS and Android: an empty screen.
* **Error:** web: an "Error" dialog, "Failed to load activity logs. Please try again.", and the list stays empty.
* **No permission:** no checks of its own.
* **Offline (mobile):** works from the device database, showing what has synced.

## Platform differences

| Topic              | Web                                                                                      | iOS                                                                                                    | Android                                                              |
| ------------------ | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------- |
| Title              | "Approval Tasks Activity"                                                                | "Task Approval Activity"                                                                               | "Task Approval Activity"                                             |
| Group: which tasks | the group's completed tasks matching the list's filters and search, as the server allows | every task of the group on the device, including deleted ones and tasks the user can't see in the list | the group's tasks the user can see, without deleted or archived ones |
| Feed: which tasks  | the site's tasks matching the feed's filters and search                                  | tasks the user can see in the site's active task groups, including archived ones                       | the same, without archived ones                                      |
| Paging             | 20 per page                                                                              | all at once                                                                                            | 20 per page                                                          |
| Event text         | English only, built as HTML                                                              | English, or in a group the event's own message text when it has one                                    | English only                                                         |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/how-the-apps-work/screens/tasks/approval-activity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
