> 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/staff/home.md).

# Home

{% 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. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/staff/home.md).
{% endhint %}

The first page of the admin app: whom to contact when something is wrong with the service, and a warning that the portal is security sensitive.

* **Where:** admin app `/home`; menu "Home", the first item. Signing in opens this page, and so does any address the app does not know, `/` included (`**` redirects to `home`).
* **Who:** anyone signed in to the admin app; the route checks only that a session exists, in the browser ([Access](https://docs.snapfix.com/how-the-apps-work/screens/staff.md#access)). The page makes no calls.
* **Feature:** [Staff admin app](https://docs.snapfix.com/product/features/staff/staff-admin.md)

## Layout

From top to bottom:

1. The heading "The Snapfix Web Admin Portal".
2. "If ANY issue whatsoever is noticed within the Snapfix service, you should contact the following people in this order. If you cannot reach anyone then continue down the list until you successfully report the issue."
3. "If the usual WhatsApp or Telegram messages are not replied to within a few seconds of sending, then call:"
4. Three contacts, one after another. Each has a first name as its heading and labelled phone numbers: the first has "UAE number", "Irish number" and "Irish landline"; the second and the third each have "Indian mobile". The names and numbers are written into the page's code, so they ship in the app's public files. This doc does not repeat them.
5. The warning "Warning: this Web Admin portal is security sensitive. NEVER give the login or password to anyone else. The site allows full unfiltered access to all our businesses and users so tread carefully."

The menu, the test banner and the footer around the page belong to the app's frame ([Staff screens](https://docs.snapfix.com/how-the-apps-work/screens/staff.md#menu-and-frame)).

## Inputs

None.

## Actions

None. The page has no buttons and no links.

## States

* **Loading:** none. The page is static.
* **Empty:** none. The contacts always show.
* **Error:** none. The page makes no request.
* **No permission:** a signed-out visitor goes to [Log in](https://docs.snapfix.com/how-the-apps-work/screens/staff/sign-in.md).


---

# 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/staff/home.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.
