> 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/rooms/area.md).

# Area

{% 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/rooms/area.md).
{% endhint %}

The tasks of one area, on the same task list screen that groups use.

![Area](https://3653879137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVVGa79QbcEkJ7n8srxe%2Fuploads%2Fgit-blob-0cc1f5b064758552c033ce6dbfabf956acc6ca58%2Farea.png?alt=media)

* **Where:** web `/area/:id/tasks`, from a card or row on [Areas](https://docs.snapfix.com/how-the-apps-work/screens/rooms/areas.md); iOS and Android: "Areas" > an area
* **Who:** any signed-in member of the selected site. The list holds the area's tasks that the user may see, as on the group task list. On the web with a multi-site selected, only the site's "Admin" role gets the create button and the "⋯" menu.
* **Feature:** [Rooms and areas](https://docs.snapfix.com/product/features/rooms/rooms-and-areas.md)

The page is the group task list ([Group tasks](https://docs.snapfix.com/how-the-apps-work/screens/tasks/group-tasks.md)) with its [changes for rooms and areas](https://docs.snapfix.com/how-the-apps-work/screens/tasks/group-tasks.md#rooms-and-areas), as on [Room](https://docs.snapfix.com/how-the-apps-work/screens/rooms/room.md). This page says only what is specific to an area.

## Layout

**Web:** the header has a back button, an area icon and the area's name (translated when the site has translation on), and, with a multi-site selected, the site's name under it. The controls row has the "Search" field, the "+" button (titled "Create") and the "⋯" menu, which holds only "Mark All as Read". Below: the same controls, view switch, counts and cards as on [Room](https://docs.snapfix.com/how-the-apps-work/screens/rooms/room.md#layout). With no tasks, the list shows "Manage your Tasks in a Snap!" and "To add a task, click on the + button."

**iOS:** the area's name and description in the header. Tapping the header opens [Area info](https://docs.snapfix.com/how-the-apps-work/screens/rooms/area-info.md). The filter button is hidden. The "+" menu is the same as on a room: "Create a new task", "Create a new Voice Task", "Share Multi Task Report (PDF)" and "Mark all as read".

**Android:** the task listing with the area's name in the header. Tapping the header, or the info icon, opens [Area info](https://docs.snapfix.com/how-the-apps-work/screens/rooms/area-info.md).

## Inputs

None of its own. Search, sort, "Display Tasks", "Assigned to me" and "Priority" work as on [Group tasks](https://docs.snapfix.com/how-the-apps-work/screens/tasks/group-tasks.md#inputs). Without the web filter button, the "Unread" filter is not offered.

## Actions

| Action               | Who                                      | What happens                                                                                                                                                                                                                         | API                                                                                                                                                                                                                                        |
| -------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Open the page (web)  | Anyone                                   | Loads the area for the header; the task list request starts at the same time. If the area can't be loaded, the page goes to `/fix`; an unknown area ID shows the alert "Resource not found".                                         | [`GET /v1/app/areas/{uuid}`](https://docs.snapfix.com/engineering-reference/api/rooms.md#get-v1appareasuuid); [`POST /v1/app/tasks/list`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptaskslist) with `areaUuid` |
| Page loaded (web)    | Anyone                                   | Reads the update flags of the listed tasks.                                                                                                                                                                                          | [`POST /v1/app/tasks/get-updates`](https://docs.snapfix.com/engineering-reference/api/tasks.md#post-v1apptasksget-updates)                                                                                                                 |
| Create a task        | Anyone; web multi-site: site admins only | Starts a new task with the area set. On the web, "+" opens [Add a Task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/add-task.md).                                                                                       | See [Add a Task](https://docs.snapfix.com/how-the-apps-work/screens/tasks/add-task.md)                                                                                                                                                     |
| "Mark All as Read"   | Anyone; web multi-site: site admins only | Sends the type `area`, which the API refuses, so nothing is marked and the alert reads "The selected type is invalid."                                                                                                               | [`GET /v1/app/tasks/mark-as-read/{type}/{itemUuid}`](https://docs.snapfix.com/engineering-reference/api/tasks.md#get-v1apptasksmark-as-readtypeitemuuid) with type `area`                                                                  |
| Open a task          | Anyone                                   | Opens the task in the area's context: web `/area/:id/task/:taskId` ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md)).                                                                         | See [Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md)                                                                                                                                                 |
| Open area info       | Anyone (site admins can edit)            | iOS and Android only: opens [Area info](https://docs.snapfix.com/how-the-apps-work/screens/rooms/area-info.md). The web edits areas in [Areas & rooms](https://docs.snapfix.com/how-the-apps-work/screens/rooms/areas-and-rooms.md). | None                                                                                                                                                                                                                                       |
| Back                 | Anyone                                   | Web: goes to `/fix`. iOS and Android: back to the previous screen.                                                                                                                                                                   | None                                                                                                                                                                                                                                       |
| Leave the page (web) | Anyone                                   | When the list showed new tasks, records that the area was visited, which clears its mark on [Areas](https://docs.snapfix.com/how-the-apps-work/screens/rooms/areas.md).                                                              | [`GET /v1/app/areas/mark-as-visited/{areaUuid}`](https://docs.snapfix.com/engineering-reference/api/rooms.md#get-v1appareasmark-as-visitedareauuid)                                                                                        |

## States

* **Loading and error:** as on the group task list ([Group tasks](https://docs.snapfix.com/how-the-apps-work/screens/tasks/group-tasks.md#states)); an area that can't be loaded sends the web to `/fix`.
* **Empty:** web: "Manage your Tasks in a Snap!" and "To add a task, click on the + button."; the apps show the group task list's empty state.
* **No permission:** none on the list. On a web multi-site, users without the site "Admin" role get no create button and no "⋯" menu.
* **Offline (mobile):** the device copy of the area's tasks.

## Platform differences

| Topic              | Web                                                 | iOS                     | Android                         |
| ------------------ | --------------------------------------------------- | ----------------------- | ------------------------------- |
| Header             | Area icon and name; the site's name on a multi-site | Name and description    | Name                            |
| Area info          | None                                                | Tap the header          | Tap the header or the info icon |
| "Mark all as read" | Fails                                               | Offered in the "+" menu | The group list's menu           |
| Back               | `/fix`                                              | Previous screen         | Previous screen                 |


---

# 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/rooms/area.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.
