Skip to main content
Use this guide to plan and check the controls around a stream. The CTRL Panel product page explains the control-panel design; 555stream covers the wider media workflow.

​
Prepare the Setup

All you need to get started is an internet-enabled device. Identify the stream, the configuration you want to use, and the person or agent responsible for operating it. Use the controls offered by your chosen setup.
1

Choose the stream and configuration

Start from the intended stream configuration or a suitable template. Keep a copy of the working configuration before making changes.
2

Prepare the controls and presentation

Select the sources, layout, overlays, and activities required by the programme. Assign only the permissions each operator needs.
3

Review before use

Preview the output at its intended size and check text, positioning, audio, and event behaviour. Confirm the configuration you intend to use before applying it to a public stream.

​
Themes and Overlays

Plan the visual elements together: colours, fonts, backgrounds, tickers, alerts, chat, and goals. Check how each element fits around the main content. Test small text, long names, transitions, and different scene layouts. Keep essential controls and information readable. Where the setup supports configuration import or export, retain a named copy so the same presentation can be reused or restored.

​
Alerts and Badges

For each alert or badge, define the event it represents and how it should appear. Examples include a follow, message, achievement, or programme milestone. Specify its duration, repetition rules, and any sound. Test duplicate events and overlapping alerts so the presentation remains understandable during busy periods. If an alert uses an onchain event, define which event counts and how the application distinguishes a submitted action from a confirmed result.

​
Access and Operator Roles

A stream needs clear authority for changing layouts, managing chat, and starting or stopping activities. Give creators, moderators, and agents the controls appropriate to their role. A particular feature may use an account, wallet, or token holding as an access condition. Its product rules should explain that condition and the access it provides. Token ownership alone does not define an operator’s permissions across the system.

​
If Something Does Not Render

Check the intended stream, selected scene, saved configuration, source visibility, and operator permissions. Compare the preview with the output. If the preview works but a connected output does not, follow that output’s integration guide. Preserve the working setup and record the error before changing or reloading a live configuration. For OBS, use OBS Integration. For broader problems, use Troubleshooting.