# Subscribers

Subscribers represent individual users (either internal or external), or can represent service accounts within an organization. Subscribers can be associated with one or many "[Subscriber Credentials](https://docs.revenium.io/ai-and-api-monetization/manage/applications)." Subscribers can be associated with zero or one [Organizations](https://docs.revenium.io/customer-and-subscriber-management/organizations).

***

#### Example Scenarios

**Internal Business Unit:**

In the `brighthealth-clinops` department, each nurse or doctor accessing LLM features (e.g., summarizing patient notes) is represented as a Subscriber.

* Subscriber Email: `nurse.a57@brighthealth.org`
* Subscriber ID: `nurse-station-a-57`
* Organization ID: `brighthealth-clinops`
* They may use multiple devices or credentials to initiate requests.

This allows BrightHealth to analyze usage by individual staff member and aggregate trends at the clinical team level.

**External SaaS Customer:**

ACME Bank uses a SaaS analytics platform built by FinPilot. Within ACME's organization, users like underwriters and analysts are tracked as subscribers.

* Organization ID: `acme-bank`
* Subscriber Emails\*
  * `underwriter.jane@acmebank.com`
  * `analyst.joe@acmebank.com`
* Each subscriber has an associated credential (e.g., API key or SSO token) that identifies the integration point or tool they used.

This model allows FinPilot to distinguish usage by role or user, supporting granular billing, support, and analytics.

{% hint style="info" %}
Many Saas Applications only track anonymous user usage. For this use case, Revenium supports the use of a subscriber\_id field which can take any value you store to track anonymous users. If at some point, an anonymous user becomes known, you can update their subscriber record with an email as well to maintain a usage history after their email address becomes known.
{% endhint %}