OVER-WATCH · CHURCH SETUPYour 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 4Confirm 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 5Set 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.