Access & Sales: from channel to subscriber

Four identities, four purposes

Use Subscribers shortcuts in the sidebar or All Access Tools to reach the full Access & Sales page. Seeing fewer tools can be correct for a restricted staff role.

1. Build a collection

1. Save your intended linear channels to Saved Library first. Catalogue-only members cannot automatically become playable saved outputs.
2. Open Collections, create a collection and select the intended saved streams, slots, native-event rules or VOD resources.
3. Use filters and search to narrow large catalogues. Review missing/unsaved members and resource warnings.
4. Save and verify the collection health before adding it to a package.

A collection organizes content. Its name is not necessarily the category shown in a player. Source migration should preserve a saved stream’s collection link; deleting and recreating the stream changes its identity.

2. Preview and publish a package

1. Create a package and attach the intended collections. Set duration, connection allowance and output rights.
2. Preview the draft. Review resolved playable channels, unavailable members, events, VOD and security restrictions.
3. Publish the intended package version. A draft alone is not what a subscriber receives.
4. When changing a package, review how existing subscriptions use published versions rather than assuming every edit immediately changes all subscribers.

3. Create the access line

1. Create/select a Customer if you need its contact record. Do not create a new customer every time you add a second line for the same person.
2. Create an Access Line and select a published package/subscription. Check the explicit expiry time, connection count and trial terms.
3. Open its access information and copy the native player, M3U, XMLTV or Xtream details.
4. Test using that line’s credentials. Do not send internal provider credentials or operator output tokens to subscribers.

Understand online counts and Connections

Access Lines shows distinct recently active channels for the line. Connections can show multiple stream activities under one playback lease; it is not necessarily one row per human or device. An idle lease is not the same as active media consumption. Filter by customer/line, service, content type, owner or delivery server to understand the activity.

UDP destination output is not a subscriber login. Multicast receivers cannot be enumerated as authenticated access lines merely because xOTT emits packets. See Monitoring for transport output and host network measurements.

Troubleshoot “17 configured, 11 visible”

1. Compare the six missing resources by saved stream identity, not only their names.
2. Inspect collection health for unsaved, deleted, detached or unavailable sources.
3. Check the subscriber’s actual published package version, expiry, output profile and any denials.
4. For events, distinguish slot grants from native-event grants. For VOD, verify publication and a usable asset.
5. Refresh/reconcile as offered and retest the same line. Creating another customer is not a repair for broken content references.

Set up a reseller deliberately

1. Open Resellers, create the partner and choose its status, parent/ownership and permitted packages.
2. Start from an appropriate permission preset/group. Review rights to create or renew lines, view credentials, manage sessions, create sub-resellers and use APIs.
3. Use the Credits action with a meaningful note. Verify the resulting ledger entry; do not edit the database balance manually.
4. Sign in through the separate reseller portal and verify only that reseller’s permitted customers, lines and packages are visible.
5. Test one sale/renewal and its credit cost before granting broader rights.

Reseller visibility is not staff administrator access. White-label branding and domains require the actual DNS/TLS deployment as well as a branding configuration.

Customer portal and device adapters

A customer portal account is optional and separate from playback credentials. Link the intended access lines, then verify the customer’s My subscriptions, Player links and Activity views. Credential rotation invalidates old links; warn users before doing it.

Access-line tools can create supported MAG/Stalker and Enigma2 adapters. Use the generated adapter details and identifier requirements rather than pasting staff credentials into a set-top box. Device compatibility must be tested; these adapters do not imply support for an arbitrary interactive DVB mosaic.

Bulk changes with a preview

Use the access-line bulk operation preview for status changes, extensions, package changes or owner transfers. Review the affected count and before/after values before confirming. “Replace remaining subscription time” is different from extending from current expiry. Do not use a large batch as your first test of a new package policy.

Commerce and API integrations

Commerce requires configured signed payment webhooks and matching package, final payment state, exact amount and currency. It is not a generic checkout integration for every provider. Configure outbound webhooks separately and verify signatures in the receiver; signing secrets are shown only when created/rotated.

Create scoped reseller/staff API clients through the relevant tools and save the credential securely. Use the authenticated Access OpenAPI contract for permissions and idempotency requirements. Revoke unused clients; a player token cannot replace a reseller/staff API credential.

Policies and audit records

Security, Audit and Connections answer different questions: what is permitted, what changed and what is playing now. Use session termination/revocation when needed rather than deleting a customer to stop one session. IP/CIDR and player rules use actual request identity; ASN/ISP rules require trusted edge enrichment configured by the operator. Never trust client-supplied forwarding/enrichment headers without a sanitizing trusted proxy.