Getting Started with AllStreamHub: A First-Time Setup Checklist

Setting up new church presentation software for the first time usually happens under time pressure: a service is coming up, the old system just broke or got too limiting, and someone needs this working by Sunday. Here's a practical, in-order checklist for getting AllStreamHub set up and ready for a first live service, without missing anything that bites you mid-broadcast.

Before you touch a single screen design

1. Create your account and confirm your plan fits your team's size. AllStreamHub's free plan works for getting started with no credit card required, and you can move to a paid tier later as your team or feature needs grow, so there's no need to over-commit before you know what you actually need.
2. Invite your core team members early, even before you've built anything. Getting your worship leader, lyrics operator, and whoever runs scripture set up with their own logins now means less scrambling on a Saturday night.
3. Decide how many screens you actually need. A single-room church typically needs one screen. If you run an overflow room, a youth space, or multiple campuses, plan those out now so you're not retrofitting screen structure the week before a launch.

Building your first screens

Start with templates rather than a blank canvas. AllStreamHub's built-in templates for scripture, lyrics, and lower-thirds are designed to get a usable, decent-looking screen running in minutes, which matters far more than a fully custom design does for your very first service.

A reasonable build order for a first-time setup:

• A scripture screen, using one of the pre-built templates, matching your usual on-screen Bible translation
• A basic lyrics screen for your worship set
• A simple lower-third template for sermon titles or speaker names

Resist the urge to perfect every detail before your first live use. It's much easier to refine a screen that's already been tested live than to keep polishing one that's never actually run under real conditions.

Connecting to OBS (or your streaming software)

Once you have at least one screen built, add it to your streaming software as a browser source:

1. Copy the shareable URL for your screen from AllStreamHub.
2. In OBS, add a new Browser Source and paste that URL in.
3. Set the source's width and height to match your actual stream canvas, so nothing gets cropped or stretched.
4. Position the source correctly in your scene, checking that it sits above your camera feed in the layering order so it's actually visible.

Because this runs as a browser source, there's nothing separate to install for the graphics engine itself. The screen updates live inside OBS the same way it does in a browser tab.

Testing before your first real service

Don't let a new setup's first real test happen live. Before your first actual service:

• Push a scripture reference, a lyric line, and a lower-third to the screen and confirm each one shows up correctly in your OBS preview
• Check text sizing and contrast against your actual camera feed and lighting, not just how it looks in the editor
• Have every team member log in from their own device and confirm they can access and control the screens they're responsible for
• Run through a rough version of your actual order of service as a dry run, including a couple of instances of pushing content live from the Real-Time Dashboard

Your first live Sunday

On the day itself, get to your setup early enough to do a final check rather than trusting last week's test. Confirm your internet connection is solid, confirm every team member is logged in and looking at the right screen, and have a simple fallback plan, even something as basic as holding the last correct screen, if something unexpected comes up.

After the first service

Treat your first Sunday as a working draft, not a finished product. Note what worked, what felt clunky, and what needs adjusting, then spend a few minutes the following week refining templates based on what you actually learned running them live. A setup that improves gradually from real use will always end up more solid than one that tried to be perfect before ever going live.