Organizations
OpusDNS uses a two-level organization model. Your account is the parent organization, and you can create suborganizations beneath it — one for each customer, department, or business unit you manage.
How organizations work
Parent and suborganizations
When you sign up for OpusDNS, you get a parent organization. This is your reseller account — it holds your billing plan, account balance, and API credentials. Underneath it, you create suborganizations to separate and manage different portfolios:
Your Reseller Account (parent organization)
├── Customer A (suborganization)
├── Customer B (suborganization)
├── Customer C (suborganization)
└── Internal Domains (suborganization)
The structure is flat — suborganizations sit directly under the parent. There are no sub-suborganizations.
The organization structure is strictly two-level. You cannot nest suborganizations within other suborganizations.
What's isolated
Each suborganization has its own:
- Domains — registered and managed independently.
- DNS zones — zones and records are scoped to the suborganization.
- Users — each user belongs to exactly one organization.
- Contacts — contacts are per-organization.
- Settings — custom attributes, locale, and configuration.
Billing: consolidated or independent
Each suborganization has one of two billing modes, chosen at creation and permanent thereafter:
- Consolidated (default) — billing flows through the parent. When the suborganization registers a domain, renews, or uses any paid service, the cost is charged to the parent organization's account balance. Consolidated suborganizations don't have their own payment methods — the parent pays for everything. This is the classic reseller model: all charges consolidate on your single reseller account.
- Independent — the suborganization is its own billing customer, with its own account balance, payment methods, and invoices. Its charges never touch the parent's balance. Ideal when a suborganization is a separate legal entity that pays for itself.
See Billing modes for how to create each kind, and Billing & transactions for tracking spending.
Charges from consolidated suborganizations are billed to the parent organization — monitor your account balance to prevent failed operations. Independent suborganizations fund themselves: a spending problem there fails their operations, not yours.
Users and access
Users belong to exactly one organization — either the parent or a specific suborganization. A user in the parent organization can manage suborganizations and their resources. A user in a suborganization can only access that suborganization's resources.
Your Reseller Account
├── Admin User (full access to parent + all suborganizations)
├── Billing User (manages invoices and transactions)
│
├── Customer A
│ ├── Customer A Admin (manages Customer A's domains only)
│ └── Customer A Tech (manages Customer A's DNS only)
│
└── Customer B
└── Customer B Admin (manages Customer B's domains only)
When creating a suborganization, you can provision users for it in the same request. You can also create users later via the User management API.
Organization statuses
| Status | Description |
|---|---|
active |
Organization is operational. |
inactive |
Organization is disabled — domains and services are frozen. |
Roles
Roles determine what permissions users and API keys have within an organization — through built-in roles or your own custom roles. See Roles & permissions for the full guide, and User management for how to assign a role to a user.
