How the system works and protects data

One service and several clients

The browser, iOS and Android use a shared service. Accounts, organizations, programs and metadata are centrally managed, while clients present them according to permissions. Refreshing a screen retrieves the current state; ordinary lists do not necessarily update live after every other person's change.

Separate features, such as Playback monitoring or notification delivery, have their own update mechanisms. Do not generalize their behavior to the whole system or expect every field to synchronize instantly between devices.

Metadata and private files

Content, metadata, permissions and relationships are stored in the database. Binary files reside in private object storage and are read through an authorized service. A document identifier alone is neither a public link nor download permission.

When backing up the system, the operator must include both data and files. Exporting only the database is not a self-contained backup of all PDFs and recordings. Organization owners should not assume they can restore deleted resources themselves using screen history alone.

Authorization for every action

The server checks authenticated membership, the current organization and the required resource scope. A hidden button is an interface aid; actual control also applies when reading and writing through the service. Platform roles do not replace organization membership.

Resources assigned to an event can be read in that event's context without giving a participant the whole library. Removing the link blocks subsequent authorized reads but does not delete a file already downloaded to a private device.

Program copies and safe changes

Events preserve selected material information from planning time. Editing the source is separate from updating future programs. Version numbers help detect simultaneous editing, while bulk operations may check their entire scope before saving.

Imports do not all follow identical partial-success rules. Always read the particular tool's summary. “Saved” refers to the relevant operation, not automatically to every later step such as email delivery or offline downloading.

The organization's everyday responsibility

1. Maintain personal accounts and assign roles according to responsibilities.
2. Check material sources and rights before sharing.
3. Verify the program, lineup responses and documents before an event.
4. Read the scope and confirmation before a permanent operation.
5. Report problems with action descriptions, without secrets or data unnecessary for diagnosis.