> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/prevent/analytics.md).

# Analytics

How Snyk Analytics reports on your security posture and program

{% hint style="info" %}
**Feature availability**\
The Snyk Analytics experience is available only for Enterprise plan customers with Group-level reporting permissions.
{% endhint %}

Build custom dashboards, access enhanced metrics, and explore analytics at the Tenant, Group, or Organization level.

The Snyk Analytics allows you to:

* Select and arrange widgets from the inventory to create a personalized dashboard.
* Access the [Saved Views](/scan-fix-and-prevent/prevent/analytics/reports-tab.md#saved-views) feature.
* Discover and access pre-built reports for specific Groups in your Organization.
* Explore issues and assets in detail directly from the dashboard.

## Data access permissions

Your Group-level permissions govern data access at the Tenant level. You view data only for the Groups you are authorized to access.

### Tenant-level analytics

Group members with reporting permissions can view their Groups on the Tenant-level analytics page.

Snyk restricts access based on Group-level permissions in both predefined and custom roles.

Users with Group reporting permissions can access Tenant-level analytics without Tenant-level roles, such as Tenant Admin or Tenant Viewer.

### Group-level analytics

Snyk restricts access based on Group-level permissions in both predefined and custom roles.

Users with Group access can view data for the Organizations associated with those Groups.

### Organization-level analytics

Snyk restricts access based on Organization-level permissions in both predefined and custom roles.


---

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

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

```
GET https://docs.snyk.io/scan-fix-and-prevent/prevent/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 `build a script that syncs our docs to a CMS` 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.
