Who can reach what, and what gets written down.
Editorial trust is on its own page — this one is about the other kind. Everything below is a control the software enforces, not an intention. Where something is your decision rather than ours, we say so.
- 05
- Roles
- Permissions the interface cannot talk you past
- 00
- Routes from us into your content
- Support access is arranged, time-boxed and recorded
- 01
- Audit trail you can read
- Every sign-in, change and deletion, with who and when
Your material stays on your installation.
The archive does not leave
Footage, recordings, stills and transcripts sit where you put them. Nothing is shipped elsewhere to be described, indexed or searched.
We hold no standing access
On a self-hosted installation there is no route from us into your content. Support access is arranged with you, time-boxed, and recorded in your own audit trail.
Retention is your setting
How long recordings are kept is a number you choose, per feed. The default is a starting point, not a limit, and lowering it deletes rather than hides.
Five roles, and permissions the interface cannot talk you past.
Five tiers, each inheriting the one below
Super administrator, administrator, editor, contributor, viewer. A viewer reads; a contributor creates; an editor changes and deletes; an administrator manages people, sources and settings.
Permission is per area, not one master switch
People, settings, written content, clips, sources and system operations are separate scopes, each with its own read, create, change and delete.
Hiding a button is not a permission
The interface hides what you cannot use, but the check that matters happens on the server, on every request. Reaching the address directly does not get you past it.
Access you can take back in one action.
Short sessions that renew quietly
A working session lasts half an hour and renews itself silently while somebody is working, so nobody is signed out mid-edit and nothing stays valid for long once they stop.
Every active session is visible
An administrator sees who is signed in, on what kind of device, from which address, when they signed in and when they were last active.
Revocation takes effect immediately
Revoke one session, every session for one person, or every session in the building. It applies on the next request rather than whenever something happens to expire.
A stolen session invalidates the rest
If an old session credential is presented again — the signature of a copied one — every session for that person is dropped rather than the one that was noticed.
Guessing is slow and then stops
Sign-in attempts are rate limited, and five failures lock that account for fifteen minutes.
What happened, who did it, and from where.
Written to, never edited
Sign-ins, failed sign-ins, sign-outs, session revocations, account and role changes, deletions and source changes are all recorded with the person, the action, the address and the time.
Readable without asking us
The trail is in the interface, filterable by action and by person. It is not an export you request from support.
Deleting content does not delete its record
A removed clip leaves the entry that says who removed it and when, which is the point of keeping the trail separate from the thing.
What procurement usually asks.
Can we host it ourselves?
That is the normal arrangement. The archive, the recordings and the transcripts sit on your installation, and for most broadcasters that is the deciding factor rather than a preference.
Who can see the audit trail?
Administrators. It is readable in the interface and filterable by action, by person and by date. It is written to, never edited.
What happens when somebody leaves?
An administrator revokes their sessions and every device they were signed in on stops working immediately — not at the end of the hour, and not when a token happens to expire.
Do you hold a copy of our material?
No. On a self-hosted installation we have no standing access to your content, and any access for support is arranged with you, is time-boxed, and appears in your audit trail like anything else.
See it against your own archive.
The useful demonstration is the one that runs on your footage and your wire feeds. Tell us how your desk works and we will show you the parts that matter — and say so where we do not help.