These guides map an industry's concepts onto the objects the platform has today (bouquets, lines, packages, partner accounts, nodes, the API). They are conceptual mappings, not industry-specific features, and a partner account is a delegated account, not an isolated tenant.
Conceptual mapping
Nothing in the panel is called a store or a franchisee. The table says which object plays which role; the chapters below set them up in that order.
| In your industry | On the platform | Where in the panel |
|---|---|---|
| Store channel or training collection | Bouquet: a named set of channels, films or series that a package grants | Bouquets, from Streams and Movies / Series |
| Store channel | Live channel: a stream with its sources, EPG and output formats | Streams → add a live stream (source URL or RTMP push) |
| Training and product video | VOD catalogue: movies and series with seasons and episodes, categories and metadata | Movies and Series, or the VOD ingest job |
| Store screen or staff access | Line: one access with its package, bouquets, expiry, connection limit and outputs | Lines → add, or activation codes, or the Reseller API |
| Franchisee account | Partner account (reseller): a delegated dashboard with credits, permissions and its own lines | Users → add a reseller; Groups for its permissions |
| Regional node | Streaming nodes: edge servers enrolled from the panel, one per site or building | Servers → add a node, installed over SSH |
| Screens or devices per line | Max connections of the line: how many devices may watch at once | The line's max connections |
Prerequisites
What to have before installing.
- A head-office server (Ubuntu 22.04 or 24.04), the installer, and a server for each region that has many stores and can be reached from them.
- The store channel content (an encoder or a looping source), the onboarding and product training recordings, and the screens or media players in the stores.
- A decision on the franchise structure: which regions get a node, and who at each franchisee manages the lines.
Infrastructure deployment
The head office first, then the regions.
- Run the installer on the head-office server and set the playback base URL to an address the stores can reach, behind TLS.
- Add the store channel under Streams and the training recordings under Movies, and check them in the web player.
- Enrol a node per region from Servers; the panel installs it over SSH, or the node enrols with a one-time code, and routes that region's stores to it.
- Create a partner account for the head-office content team with permissions for the catalogue and none for the stores' lines.
Content organisation
The store channel and the training library.
- Create a live stream for the store channel and put it in its own bouquet.
- Create categories per topic and a series per training course, with one episode per lesson; add one bouquet per role (sales staff, managers, new starters).
- Create one package for the store screens and one package per role, each granting its bouquets and carrying the access period as its duration.
- Give franchisees the packages they may sell on to their stores and staff.
Partner (reseller) configuration
One partner account per franchisee.
- Create a group with permissions limited to lines, with no catalogue changes.
- Add each franchisee under Users → add a reseller, with that group, its packages and a credit balance.
- A franchisee with several regions can add a sub-reseller per region, each with its own stores.
Store and staff line configuration
A line per screen and per employee.
- Create one line per store screen under Lines → add with the store's name and the store package; the franchisee does the same for its own stores.
- Set max connections to the number of screens in the store, and to two for an employee (shop floor and phone).
- Bind a store line to the store's address when the store has a fixed one, so the credentials do not work elsewhere.
- Configure the screen's player once (M3U, Xtream Codes API or the web player address) and keep the credentials in the store's file.
Training and product video
The library for staff.
- Upload each training course as a series and each product film as a movie, or ingest them with the VOD ingest job into the media root.
- Put the recordings in the bouquet of the right role through their categories.
- Check what each role sees with a test line before opening the library to the franchisees.
The store channel
One channel for all the screens.
- Add the store channel as a live stream, fed by the head office's encoder over RTMP or by a looping source.
- Enable catch-up for the training sessions that go out live, and upload the recording to the library afterwards.
- The nodes in the regions take the channel once from the origin and serve their stores, so the stores' links are not saturated.
Expiry and renewal
Access follows the store or the contract.
- A line expires at the end of its package's period; the franchisee renews it with a package or a credit.
- Disable the line of a closed store or a leaving employee.
- Subscribe the franchise-management or HR system to the webhooks to see lines that are about to expire or already expired.
Integration with franchise or HR systems
Systems drive the lines; the player plays.
- Create a Reseller API key for the franchise-management or HR system; it calls create_line, renew_line, enable_line and disable_line, with a request id on each write.
- Use a commerce connector when you bill franchisees for the service; any other system uses the Reseller API and webhooks.
- There is no single sign-on for viewers: staff sign in to the player with the credentials of their line.
Security considerations
Keep each store on its own lines.
- Serve the panel behind a reverse proxy with TLS and set TRUSTED_PROXIES so the audit log and the IP rules see real addresses.
- Two-factor sign-in for every head-office account; franchisees get a permission group limited to their own lines.
- A connection limit per line, signed and expiring playback links, and address binding for the store screens.
- Enable the encrypted database backup with an off-site copy, and use the audit log to review changes of lines and catalogue.
Troubleshooting
The usual first checks.
- A store screen is black: check that its line is enabled and not expired, the address binding, and the connection limit if a second device is using the line.
- A region buffers: check the regional node's heartbeat and that the stores are routed to it.
- A franchisee cannot create lines: check its credit balance, its group permissions and the packages assigned to it.
- The audit log shows the proxy's address: set TRUSTED_PROXIES to the proxy and restart the panel.