Authorize 4ALL Signal, License a Workstation, and Select a Workspace

Complete browser authorization, confirm the device license, and select the correct organization and team.

Written By 4ALL.LIVE

Last updated 17 days ago

Authorize the Signal desktop application, bind the workstation to a valid device license, and select the organization and team that own the live event.

Best for: operators signing in on a new workstation, changing workspaces, or resolving a license state before production.

Authorize the application

  1. Start authorization from Signal. The application opens a browser-based PKCE flow and waits for a localhost callback.
  2. Complete sign-in and approval in the browser on the same workstation.
  3. Return the callback within the 15-minute window. If the window expires, start a new authorization attempt.
  4. Back in Signal, select the correct organization and team for the event.
  5. Confirm that the workstation reaches Licensed before starting a production pipeline.

Signal stores its authorization tokens in the operating system credential vault. Do not copy, export, or share credential-vault contents.

Read the authorization and license states

  • Licensed: the device has a current server-issued lease and can be used within its authorized capacity.
  • Offline grace: Signal cannot currently refresh the lease but may continue only until the server-issued lease expires.
  • License required: no usable device license is available; active production use is blocked.
  • Update required: a mandatory application update must be applied before operation continues.
  • Authorizing: the browser flow or callback is still in progress.
  • Error: authorization or license validation failed; inspect the displayed details and restore the failed prerequisite.

Important: offline grace is not offline LL-TTS. Signal receives server-generated audio and cannot create LL-TTS locally. Network access, valid credentials, event publishing, and LL-TTS entitlement remain necessary.

Verify the workspace

  • The displayed organization and team match the event owner.
  • The state is Licensed, or a deliberately assessed offline-grace window remains valid.
  • The expected event appears when a TTS node refreshes its event list.
  • A test pipeline can start and stop while the workstation is off air.

Troubleshoot

  • If the localhost callback does not complete, keep Signal running, use the same workstation browser, and restart authorization within a fresh 15-minute window.
  • If no event appears, recheck the selected organization and team, network access, event availability, and authorization.
  • If the license is revoked or expired, stop relying on the pipeline and have the license restored by an authorized 4ALL team member.
  • If Update required appears, move to fallback and update off air. Mandatory updates and revoked or expired licenses stop active pipelines.

Security and capacity boundary

A Signal device license is separate from LL-TTS usage and external equipment or labor. A 4ALL team member must validate the workstation, license, and physical I/O capacity; do not infer capacity from a successful sign-in alone.