# Organizations

Organizations can be internal business units, customers, or both. Organizations are created or saved with data sent in the `organization_id` parameter in Revenium's SDKs.

[Subscribers](https://docs.revenium.io/customer-and-subscriber-management/subscribers) are generally associated with Organizations to allow you to map usage for multiple subscribers within a single organization. This allows you see a rolled-up view of all subscribers by Organizations, which could represent an end customer or an internal department.

***

#### Example Scenarios

**Internal Business Unit:**

The "BrightHealth System" hospital network uses Revenium to track usage by its **Clinical Operations** department. Instead of tracking usage for the entire organization with one ID, they create separate `organization_id` values for internal departments to support granular reporting.

* Organization ID: `brighthealth-clinops`
* Subscribers represent individual care providers or internal services.
* This approach enables tracking cost and usage trends per department, supporting internal budgeting and cost center allocations.

**External SaaS Customer:**

A B2B fintech company, "FinPilot", uses Revenium to track usage by its external customers.

Each customer has a unique `organization_id`., and each subscriber is tracked by both a `subcriber.id` and a `subscriber.email` For example:

* Organization ID: `acme-bank` (you can choose to save names or Ids in this field depending on how you wish to alias customers in Revenium)
* Subscribers represent Acme Bank employees using FinPilot tools (e.g., risk scoring or credit analytics).
* This setup enables ACME to receive usage-based billing, while FinPilot sees total usage grouped by each customer org.