> For the complete documentation index, see [llms.txt](https://docs.opendatablend.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opendatablend.io/subscription-management/managing-analytics-users.md).
# Managing Analytics Users
When you sign up to an [Analytics Plan](https://www.opendatablend.io/pricing) you are given the option to specify the email addresses of the [Analytics Users](/open-data-blend-analytics/analytics-users.md). You are also given the option to treat the email address of the subscription account holder as an Analytics User (this is ticked by default).
You can update either of these from the subscription portal. From the subscription portal Home page, click 'View More'.
Click the edit icon in the Account Details section.
The 'Email is Analytics User' refers to the email address that is used to log into the subscription portal. You can check or uncheck this as needed.
To update the Analytics Users, simply provide a semi-colon (';') separated list of email addresses e.g. `user1@yourdomain.com;user2@yourdomain.com;user3@yourdomain.com;`
{% hint style="info" %}
The semi-colon separated list of Analytics User email addresses is like the 'To' line of an email. Each user in the list will receive an invite to Open Data Blend Analytics and their activity will be linked to your subscription.
{% endhint %}
{% hint style="danger" %}
If an email address is already linked to another Analytics Plan subscription, only the link to the active subscription that was created first will be honoured for billing purposes.
{% endhint %}
---
# 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.opendatablend.io/subscription-management/managing-analytics-users.md?ask=&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.
