> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/analytics/who-can-access-analytics-and-how-permissions-work.md).

# Who Can Access Analytics and How Permissions Work

This article explains who in your organization can see Analytics today, what to do if someone needs Analytics visibility without being involved in day-to-day AR, and how to add a new dashboard user.

***

### Who has access today

Analytics is an add-on product. It is not included in the Accounts Receivable dashboard by default, and it will not appear in your navigation unless your organization has Analytics.

Once your organization has Analytics, access to it is not separated from access to the rest of the dashboard. Anyone with an active login to your Partner Dashboard will see the **Analytics** tab, regardless of the role assigned to them.

{% hint style="info" %}
**Note**: If you do not see Analytics in your dashboard and would like to, reach out to your account manager or email <customersuccess@alternativepayments.io>.
{% endhint %}

***

### If leadership needs Analytics but not AR visibility

There is no way today to give someone Analytics without also giving them access to the Partner Dashboard. If you have leadership or operations staff who need the numbers but are not involved in day-to-day AR, there are a couple of options:

* **Export and share reports.** Pull the reports they need from Analytics and share the export with them, so they get the figures without needing a login of their own.
* **Add them as a dashboard user with a limited role.** Assign a role that matches how much they should be able to do in AR. See [User Roles](https://help.alternativepayments.io/preferences/user-roles-and-team/user-roles) for what each role can and cannot do — **Read-Only**, for example, allows a user to view invoices but not edit them, change bank information, or alter integrations and automations.

Your CSM can help you work out which approach fits your team. Reach out to your account manager or email <customersuccess@alternativepayments.io>.

***

### Coming soon: Analytics-specific read-only access

We are working on dedicated permissions for Analytics. This will let leadership and operations staff view Analytics without being involved in day-to-day AR.

This is not available yet. We will notify partners once it is released.

**Love our platform?** Rate us on [Channel Program](https://channelprogram.com/v/alternativepayments) and check out our [Referral Program page](https://www.alternativepayments.io/referral-partners/)!


---

# 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://help.alternativepayments.io/analytics/who-can-access-analytics-and-how-permissions-work.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.
