Relationships

Relationships

Overview

The Relationships area manages the distributor, partner, and tenant hierarchy used byacross subscriptions, users, billing, commissions, documents, and document visibility.dashboards.

Relationship Hierarchy

CMS uses this ownership chain:

Distributor
  -> Partner
       -> Tenant
            -> Subscription

Platform administrators can work across the whole hierarchy. Distributor, partner, and tenant users arework limitedonly toinside their assigned organisation scope.

Creating Records

New distributor, partner, and tenant creation uses stepper-style forms withuse validationstep-by-step screens. Each step validates the entered information before the record is saved.created.

Record	CapturedKey details
Distributor	Display name, description, billing contact, billing address, billing country, and billing currency.
Partner	Display name, distributor, description, billing contact, billing address, billing country, and billing currency.
Tenant	Details,Tenant details, billing details, and summary confirmation.

New partner and distributor forms loaduse the platform default currency fromunless DefaultPlatformCurrency.the user selects another currency.

Relationship Pages

The top-level Relationships page containsgives authorised users access to distributor, partner, and tenant management surfaces.management. Detail pages show related records and operational widgetsviews such as consumption, commissions, tenants, partners, subscriptions, invoices, and documents where relevant.available.

The portal checks prerequisites before loading scoped grids:

• Partners needIf a distributorgrid scope.
is
• Tenantsempty needor replaced by a partnersetup scopemessage, forcheck platformwhether prerequisite records exist. For example, partners require a distributor, and distributortenants roles.
generally
• Partnerrequire rolesa load tenant summaries through server-side scoped tenant routes rather than partner-level summary access.

partner.

Self-Provisioning

Some delegated creation actions can be enabled or disabled in settings. Platform administrators can still create tenantsrelationship regardlessrecords ofdirectly. Read-only roles can view records but cannot create or change them.

Access

Relationship access follows the organisation hierarchy.

User scope	Typical visibility
Platform	All distributors, partners, and tenants.
Distributor	The distributor, its partners, and related tenants.
Partner	The partner and related tenants.
Tenant	The assigned tenant.

If a user cannot create or edit a relationship record, check their role, their organisation assignment, and any self-provisioning settings for that record type.

Billing and Commissions

Distributor and partner detail pages can show consumption and commission information where the user has access. Commission views are limited to the partner or distributor tenantscope self-provisioningavailable settings. Platform readers remain read-only.

Delegated creation and lifecycle actions are controlled by settings for the relevant role family. The portal hides actions when settings disable self-provisioning, and the API enforces the same boundary.

Security and Scoping

Tenant create and update validates the target partner throughto the signed-in user's hierarchy before saving. Partner update validates the target distributor through scoped distributor access before saving.

These checks prevent delegated administrators from attaching records to distributors, partners, or tenants outside their permitted hierarchy.

Billing and Commission Relationships

Partner and distributor commission generation uses billing rows in the selected month. The month end is treated as the first day of the next month so full-month rows ending on day one of the next month are included.

Commission chart routes validate non-platform access to the requested partner or distributor before returning chart data.user.

Related Pages

• Subscriptions and Resource Groups
• Usage, Billing, and Invoicing
• Settings and Operations