> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/passwordless-for-web-apps/analytics.md).

# Analytics

The Analytics Dashboard gives Community Administrators a graphical overview of user activity across the tenant. Data can be filtered by today, last 7 days, last 30 days, or a custom date range.

***

#### What's on the Dashboard

**Summary metrics** at the top show four numbers for the selected period:

| Metric                   | Description                                            |
| ------------------------ | ------------------------------------------------------ |
| **Unique Users**         | Users with at least one authentication                 |
| **Total Logins**         | All login attempts across all applications and methods |
| **Failed Logins**        | Number of failed login attempts                        |
| **New Devices Enrolled** | Devices registered during the period                   |

**Charts** below the summary provide a breakdown of activity:

* **Successful Authentications** — logins over time, broken down by authentication method; toggle between numbers and percentage view
* **Application Usage** — total logins per SAML and OIDC application
* **Failed Logins** — failed login count with reasons for failure
* **New Devices** — new device enrollments per day


---

# 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.1kosmos.com/authentication/passwordless-for-web-apps/analytics.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.