Subscribers¶
A subscriber is your customer — the subject of entitlements. Not a person on your team, and not your organization.
Why “subscriber”¶
They subscribe to a plan. The name matches the commercial relationship and avoids colliding with:
- User — someone on your team who signs into e10s
- Organization — your vendor account
Properties¶
| Field | Description |
|---|---|
id |
e10s id (use in check APIs) |
external_id |
Your system’s id (optional, unique per org) |
name |
Display name |
created_at / updated_at |
Timestamps |
Store external_id so you can map tenant_id / customer_id from your DB without inventing a parallel id scheme (you can still use e10s id everywhere if you prefer).
Lifecycle¶
- Customer signs up in your product
- Your backend creates a subscriber in e10s
- You create a subscription to a plan
- All entitlement checks pass
subscriber_id
Isolation¶
Subscribers belong to exactly one organization. You cannot read another vendor’s subscribers.