Appearance
Who may watch
Who may watch is your portal's decision: it knows the subscribers, their boxes and packages. Flowtrix checks only that each request carries a token signed by a portal it trusts, for this path, and not expired. Set it up under Access.
Signed links
A link carries ?token=<expiry>.<signature>, signed for a stream's folder (/news-24/, /vod/7/films/):
https://tv.example.com/news-24/index.m3u8?token=1793995200.Xq3…The token is copied into every playlist and segment, so one token plays the whole stream. A refused request is a plain 401.
Token issuers
Each portal that signs links is an issuer with its own secret. Under Access › Token issuers (admins):
| Setting | Meaning |
|---|---|
| Secret | Made by Flowtrix and shown once, or pasted to keep a portal's existing one. Kept encrypted; its fingerprint tells which secret a portal has |
| Scope | Live, VOD or both, and optionally only some channels |
| Longest token | Tokens that expire further ahead are refused, so a leaked secret cannot sign a link for a year |
| Check URL | Optional: Flowtrix asks your portal before a viewing session plays, and keeps its answer for a while (60 s by default). With no answer in 3 seconds, it plays unless you choose to refuse |
Rotate gives a new secret and keeps the previous one valid for an overlap (24 hours by default), so you can put the new one in the portal. Disable or remove stops an issuer's tokens on the next request.
At the first start, FLOWTRIX_SECRET becomes the issuer "Default", so links signed before keep playing. Rotate it to give your portal its own secret.
Public channels
A channel marked public plays without a token, e.g. a test card.
Viewers
Viewers shows who is watching what now: live, catch-up or VOD, from which address, since when, and with which issuer's token (8 characters of it, never the whole token).
Block refuses that session's token on every address until it expires: one box cut off at once, without rotating the issuer. Blocks last until Flowtrix restarts; for good, rotate the issuer.
API keys
Scripts and Mintrix use API keys (Access › API keys), each with a role. Mintrix's key may add, edit, start and stop channels only; deleting, VOD, access, users and settings stay in Flowtrix's own interface.