Access Policy for Each Broadcast

Who enters, from how many devices, how many viewers simultaneously, and what is allowed with the content - all in the broadcast's own settings.

The Settings

Each broadcast carries its own policy. The organization manager edits it on the broadcast page:

How to enter: personal code, shared code, or both.
Single active session per code: enabled or disabled.
Allowed devices per code: 1 to 5.
Simultaneous viewer cap per broadcast (or no cap, up to the organization's quota).
On-screen watermark: enabled or disabled.
Recording: enabled or disabled.
Blocking player embedding on other websites.
Blocking download.

Changes Apply to New Entries

When a new policy is saved, it applies to every viewer who enters from that moment. Those already inside continue until their token expires (up to two minutes) and then align. Increasing the number of allowed devices also applies to codes already issued - there is no need to re-issue them.

Every Change is Documented

Policy changes are recorded in the audit log with the full state before and after: who changed it, when, and exactly what. If the change cannot be recorded - it is not performed. This is important when several managers work on the same organization.

Frequently asked

Can a default policy be set for the organization?

Currently, every broadcast is created with the strict default settings (personal code, single session, one device, watermark and recording enabled). An organizational default policy - coming soon.

Can an operator change the policy?

No. An operator sees the policy of the broadcast they are assigned to, but only an organization manager can change it.