OVER-WATCH · CHURCH SETUP

Your locations.
One place to watch.

A guided setup for a separate, view-only monitor for your church. You handle the Resi account steps; your setup contact handles hosting and verifies the connection with you. This guide does not collect credentials or submit a signup.

0 of 6 steps complete

STEP 1

Start with the right Resi account

Sign in to Resi Studio using your own church account. Ask your Resi administrator to join you if you cannot access account settings.

Confirm that each location already has an encoder in Resi. Over-Watch watches existing feeds; it does not start broadcasts, add destinations, or change production routing.

STEP 2

Check API access before doing anything else

Open Settings → API Access in Studio. Resi documents Go Live API eligibility for Pro or Enterprise Multisite and/or Live Streaming plans. If API Access is missing, ask Resi to confirm your plan and permissions. You do not need to purchase or change anything to complete this checklist.

Resi’s official API guide

STEP 3

Create a dedicated connection

  1. In API Access, select + API Client (the label may say +Add API Client).
  2. Name it Over-Watch Monitor so it is easy to identify later.
  3. Ask Resi which minimum roles allow encoder status, event discovery, and authorized HLS preview access. On Demand access alone is not a substitute for live encoder access.
  4. Review and accept Resi’s terms yourself, then choose Generate Token.
  5. Copy the Client ID and Client Secret to your church’s password manager.

Resi’s Go Live role includes broadcast controls. Over-Watch exposes no broadcast controls, but a credential with that role can have broader powers outside the monitor. Ask Resi whether read-only credentials are available. Do not reuse another church’s credential.

STEP 4

Confirm the details that connect your feeds

Your setup contact needs the church’s customer/account ID and confirmation that the integration may read encoder/event data and HLS previews. These account-specific details are not always exposed in the same place in Studio. Use this request rather than hunting through browser tools:

We are connecting a view-only Over-Watch monitor to our own Resi account. Please confirm our customer/account UUID and the minimum API permissions for reading all encoders, current events, and authorized HLS previews. Please confirm whether the encoder/event discovery endpoints used by this integration are supported for our account. We do not want broadcast start/stop permissions if a read-only option is available. If a broader role is required, please explain the scope before we enable it.

Your setup contact can identify media profile names from authorized event URLs during verification. You should not need to find bucket names or individual encoder IDs yourself. For a combined two-channel source, identify its encoder by the name shown in Studio.

STEP 5

Set up your church’s own monitor

Give your setup contact your church name, logo you have permission to use, preferred URL, and contact person. Arrange an approved secure handoff for the API secret, or enter it directly into your church’s encrypted hosting settings with their guidance. Do not paste it into this guide, email, a shared chat, or a website’s source files.

Your setup contact provisions a separate site and database, saves your credentials server-side, configures your customer ID and verified media profiles, and tests the connection. They also create a unique page password. Your normal Resi password is never needed.

STEP 6

Choose your feeds and test together

  1. Open your new monitor and sign in with its page password.
  2. Open Settings, choose encoders, and save. The selection is shared with your church’s viewers.
  3. During an already scheduled live stream, confirm names, video, audio, meters, solo, and full screen. The monitor cannot start a test broadcast.
  4. Use a recording and Test ending to check the blurred last frame. A recording test is not a live test.
  5. Check on a phone and laptop; add it to the Home Screen if useful.
  6. Share only your monitor URL and its page password with approved viewers. Do not share the API secret.