xOTTSettings, staff and maintenance
Set global defaults without confusing them with service, stream, subscriber or storage-specific controls.
On this page
Choose the narrowest appropriate scope
| Scope | Examples |
|---|---|
| Global Settings | UI defaults, notifications, session/security policy, recovery defaults, VOD defaults, M3U formatting and license. |
| Service Outputs | Service/account outputs, event slots, automatic arming and stream defaults. |
| Stream settings | Exact tracks, logo, outputs, processing and placement overrides. |
| Subscriber package / line | Content rights, expiry, connections and output permissions. |
| VOD destination / worker folder | Storage location and where processing executes. |
Save only the section you intend to change and check its validation. A global setting is not proof that every existing per-stream override has been removed.
Restart and recovery defaults
Set retries, delays and cooldowns with the provider and network in mind. Unlimited retries do not mean an endlessly failing stream should appear healthy. Distinguish process restart, saved-stream recovery, event auto-start and ordered source failover; they have different eligibility and lifecycle rules. Aggressive retries can make a provider outage worse.
Staff roles and sessions
Create internal users under Administration → Staff. Grant content, monitoring, infrastructure, subscriber or administrative permissions intentionally. A support role should not need owner access simply to inspect a subscriber.
Use My Account to review active staff sessions and revoke unfamiliar ones. Missing historical device/address metadata is not a reason to invent an identity. Player access lines, reseller accounts and staff sessions remain separate.
Protect staff sign-in
Where offered in My Account, set up authenticator-based two-factor authentication using your current password. Store the secret/setup URI securely, enroll it in your authenticator and verify a six-digit code before relying on it. Do not include the setup secret in support screenshots. Review active sessions after any suspected compromise.
Security configuration
- Use HTTPS for credentials and secure browser sessions.
- Configure administrative IP restrictions with a tested recovery path.
- Use the explicit HTTP player-login exception only where you understand the exposure.
- Grant API clients only their needed scope and rotate compromised credentials.
- Treat generated playlist and playback tokens as credentials; do not paste real links into public tickets.
Downloads and media defaults
Global VOD path, concurrency, quality/language defaults and history retention apply to the relevant main-server jobs and new dialog defaults. Worker roots are configured on the worker; generic cloud/SFTP transfer still needs local staging. Cleaning completed job history is not equivalent to deleting media files.
Backups and updates
Use Operations → Database to create and verify backups before changes. Keep an independent copy and a restoration plan. Media files, external mounts, secrets and system networking may require separate backups. Update main and workers together and verify actual playback afterwards. See the update recipe.