> 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/security-dashboard.md).

# Security dashboard

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

Staff open the monthly Google Sheets behind the security and registration dashboards. The list of links is built into the app, so the page calls no API.

* **Where:** admin app `/security-dashboard`; menu "Security Dashboard".
* **Who:** any signed-in staff user. The route checks only that a session exists.
* **Feature:** [Usage dashboards](https://docs.snapfix.com/product/features/staff/usage-dashboards.md)

## Layout

No page title. Two sections, in the order of the built-in list, side by side on wide screens and stacked on narrow ones. Each has:

1. Its name as a heading: "Security Dashboard" or "Registration & Active User".
2. A divider, then "Description:" and the section's text: "Security dashboards are updated every hour and provide sms event count and user details derived from BigQuery." or "Registration and active user dashboards are updated every hour and provide event count and user details derived from BigQuery."
3. "Sheet Links", with one link per month, "2023-01" to "2023-12". Each opens its Google Sheet in a new tab.

The list is `src/sheets.json` (webadmin\_angular @ db972390b8). It stops at 2023-12 \[[ASK-216](https://github.com/snapfix/docs/blob/main/ASK.md#ask-216-should-the-security-dashboard-list-months-after-2023-12)]. The build also copies the file into the app's public assets (`angular.json:32`), so anyone can read the links without signing in. Whether the sheets themselves are shared beyond staff is not recorded in any repo \[[ASK-215](https://github.com/snapfix/docs/blob/main/ASK.md#ask-215-who-can-open-the-security-dashboards-sheets)].

## Inputs

None.

## Actions

| Action              | Who   | What happens                                                   | API  |
| ------------------- | ----- | -------------------------------------------------------------- | ---- |
| Open a month's link | Staff | Opens that month's Google Sheet in a new tab, outside the app. | None |

## States

* **Loading:** none; the list is part of the app.
* **Empty:** none in practice. The page shows "No Data Available" only if the imported list is missing; an empty list would show an empty page (`src/app/pages/security-dashboard/security-dashboard.component.ts:19`, `.html:1`, `:23-25`).
* **Error:** none; the page makes no request.
* **No permission:** none in the app.

## Dialogs and sheets

None.


---

# 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/security-dashboard.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.
