Topic 1 of 13
#Controls shown on every page
The top bar tells you whether BrightBridge is ready and gives you a few actions that apply to the whole portal. Check it before working in a page.
| Control | What it means | What a new operator should do |
|---|---|---|
| Config loaded | BrightBridge has loaded the settings it needs to operate | If it says not loaded, stop and report the message rather than attempting work |
| Serving enabled | Player content serving is switched on | Treat disabled as a service warning and follow your escalation process |
| Settings changes | Someone has edits waiting for review or application | Do not apply another person's changes; open the summary only to identify the owner |
| Light / Dark | Changes only how the portal looks in your browser | Choose whichever is easiest to read; it does not affect players |
| Your name | Shows which account will be recorded for actions | Make sure it is your own account before changing anything |
| Refresh | Reloads current information from BrightBridge | Use once when information looks old; wait for it to finish before trying again |
| Logout | Ends your signed-in session | Use at handover or when leaving a shared computer |
| Logs drawer | Shows recent operator-visible messages without leaving the page | Open it after an error and copy the relevant time and message before dismissing anything |
Topic 2 of 13
#Dashboard: every card explained
| Card or control | What it shows | Beginner response |
|---|---|---|
| Players | Known players plus recent, pulling and offline counts | Use it to spot an unusual count, then investigate in Players |
| Deployments | Presentations in the library and presentations currently active | Use it as a quick sense check, not as proof that every screen is correct |
| Serving | Whether content serving is available | Escalate an unexpected disabled state |
| System metrics | Current processor, memory and network activity | Look for a warning or an obvious change from normal; do not diagnose from one number alone |
| Uptime + Load | How long the service has run and its recent workload | A very short uptime may explain a recent restart; record it if investigating an incident |
| System warnings | The most important current platform warning | Open the relevant workspace or report the exact wording |
| Disk usage | Used and free storage across important locations | Escalate warnings early; do not delete files manually |
| Open file host | Opens the player-facing content host | Use only for an approved availability check; it is not the presentation library |
Topic 3 of 13
#Players: list, search and selection
| Control | What it does | Safe first use |
|---|---|---|
| Refresh | Reloads the player list and recent activity | Click once, wait, then check the updated time or count |
| Add / setup player | Prepares approved setup material for a known device | Use only with a confirmed player identity and site instruction |
| Search serial, label, model, tag | Narrows the visible player list | Clear old text first, then search with one reliable identifier |
| Player row | Opens that player's details | Match the label, identifier and site before using tools |
| Status badge | Summarises how recently the player reported | Compare it with the site's operating schedule before calling it a fault |
| Model and presentation | Shows recognised hardware and reported content | Use as identity and version clues, then confirm with activity or a visual check |
Topic 4 of 13
#Player details: status panels and read-only checks
| Panel or control | What it tells you | How to use it |
|---|---|---|
| Player heading | The friendly label or hostname for the open player | Reconfirm it whenever you return from another tab |
| Activity / last check-in | When the player most recently contacted BrightBridge | Compare the time with the expected reporting interval |
| Current presentation | The content identity most recently reported | Compare it with the approved release name |
| rDWS Metrics | Remote device status such as info, health and video mode | Refresh once and read the friendly summary before opening raw details |
| Raw metric payloads | Technical evidence behind the summary | Leave collapsed unless support asks for a specific value |
| Storage bar | Reported used and available player storage | Escalate low-space conditions; do not guess which files to remove |
Topic 5 of 13
#Player Tools, Liveview and Logs
| Control | What happens | Beginner rule |
|---|---|---|
| Refresh tools | Reloads clock, timezone, storage and other supported tool results | Start here before changing anything |
| Timezone selector | Chooses the approved timezone to send to the player | Change only when the current value is proven wrong and the target is confirmed |
| Save timezone | Applies the chosen timezone | Record the old value and verify the player's next check-in |
| Take snapshot | Requests one still image of the current output | Prefer this before starting continuous Liveview |
| Reboot | Restarts the player and interrupts playback | Use only in an approved window after read-only checks fail |
| Ping | Runs a lightweight network reachability check | Use one preset once; record the result and time |
| Liveview tab | Starts or displays a continuous remote screen view | Start one session, wait for its state, and stop it when finished |
| Pop out | Opens the current Liveview in a separate window | Use only when you need more space and screen content is safe to display |
| Logs tab | Shows logs reported by the selected player | Fetch once after reproducing the issue and focus on the matching time |
Topic 6 of 13
#Deployment: player panel
| Control | What it changes | How to avoid mistakes |
|---|---|---|
| Search players or tags | Narrows the visible deployment targets | Clear it before beginning a different release |
| Group filter | Shows players in one saved folder or tag grouping | Confirm the group matches the approved target list |
| Select visible | Selects every currently visible player | Use only after checking the filter and visible count |
| Deselect visible | Removes visible players from the selection | Read the selected count afterward because hidden selections may remain |
| Player checkbox | Adds or removes one player from the release scope | Use individual checkboxes for small or unusual releases |
| Player disclosure | Expands labels, model, tags and removal tools | Use for organising a player; these edits are separate from content release |
| Save / Reset label | Changes or restores the friendly player name | Use an agreed naming pattern and verify the identifier before saving |
| Model override | Records a device model when automatic identity is unavailable | Leave unchanged unless the real hardware model is confirmed |
| Add / remove tag | Changes operator grouping labels | Use established tags; remember this can affect future filtered selections |
| Remove player | Deletes the player's BrightBridge records and content history | Do not use for an offline player; follow the retirement procedure |
Topic 7 of 13
#Deployment: presentation library
| Control | What it does | Beginner rule |
|---|---|---|
| Folder | Chooses a published presentation folder for upload | Select the folder that directly contains the approved published files |
| Zip | Chooses a zipped published presentation | Use a clean approved archive, not a general project backup |
| Upload / Clear | Adds the selected content or resets the uploader | Read inspection warnings before accepting the upload |
| Folder filter | Narrows the presentation library | Clear it when a presentation appears to be missing |
| Presentation row | Selects content for the release panel | Confirm its name, source and inspection status |
| Rename | Changes the friendly library name | Keep the release identity and version recognisable |
| Set Folder | Organises the library item into an operator folder | This does not release the presentation to players |
| Delete | Removes the library item | Confirm it is obsolete and not needed for recovery before deleting |
| Utility settings | Configures approved connection-test behaviour for compatible content | Leave organisation defaults unchanged unless following a test plan |
Topic 8 of 13
#Deployment: release, dry run and rollback
| Control | What it means | Required check |
|---|---|---|
| Selected count | The exact number of players the release can affect | Match it to the approved target count |
| Selected presentation | The library item that will be released | Match its name and version to the change request |
| Rewrite base URLs | Adjusts presentation addresses for the target environment | Use the organisation's normal setting unless the release plan says otherwise |
| Rewrite device IDs | Adjusts player-specific device identity references | Use only when the presentation and process require it |
| Variable overrides | Sets approved values per selected player | Check every player/value pair and avoid private data |
| Advanced deployment options | Shows less-common release behaviour | Leave collapsed and unchanged for normal releases |
| Run Dry Run | Previews validation, warnings and intended changes without replacing live content | Run after the final player, content and option choices |
| Technical details | Shows deeper dry-run evidence | Use when resolving a warning or when support asks |
| Overwrite acknowledgement | Confirms you understand selected live folders will be replaced | Tick only after reading the current dry run |
| Deploy | Starts the live content replacement job | Click once, keep the page open and read per-player results |
| Rollback player / Load | Loads saved restore points for one player | Confirm the affected player before loading backups |
| Restore | Replaces current content with the selected known-good backup | Use an approved restore point and verify playback afterward |
Topic 9 of 13
#Utility Tools: result columns
| Column or control | Plain-English meaning | How to read it |
|---|---|---|
| Refresh | Reloads recorded connection-test results | Use once, then check the newest Date Time |
| Latest median | The middle observed speed in the newest test | Usually more useful than one unusually fast or slow sample |
| Latest mean | The mathematical average of the newest samples | Compare with the median to spot uneven results |
| Downloaded / Time taken | How much test data moved and how long it took | Compare only tests using similar settings |
| Player | The player that reported the result | Confirm the friendly name and identifier |
| Service / Server | The test method and destination | Compare like with like |
| Samples | How many observations contributed | More samples usually give a steadier picture |
| Trigger | What caused the test to run | Use it to distinguish scheduled and manually requested evidence |
Topic 10 of 13
#Multiview: presets, tiles and display controls
| Control | What it does | Beginner guidance |
|---|---|---|
| Preset | Loads a saved monitoring layout | Choose by the agreed site or event name |
| Preset name | Names the current layout | Use a clear purpose, not a person's temporary note |
| Selected / running | Counts configured sources and active Liveviews | Check these before starting or stopping all |
| Start all | Starts every configured player Liveview | Use only for the required tiles; large grids use more resources |
| Stop all | Ends all running player views in the grid | Use when monitoring is complete |
| Fullscreen | Expands the whole monitoring grid | Exit fullscreen before editing tiles if controls are hard to find |
| Save / Duplicate / New blank | Maintains reusable layouts | Duplicate a shared preset before experimenting |
| Refresh | Reloads layouts and player information | Do not use repeatedly while tiles are connecting |
| Delete preset | Removes the saved layout | Confirm no team relies on it |
| Layout size | Chooses the number of rows and columns | Use the smallest grid that meets the monitoring need |
| UMD controls | Show and style player name labels | Keep labels on when similar screens could be confused |
| Tile source | Chooses Empty, Clock, Fleet Health or a player | Pick one purpose per tile and verify the player label |
| Start / Full / Stop | Controls one tile | Prefer one-tile actions when investigating a single screen |
Topic 11 of 13
#Users: account controls
| Control | What it does | Safety rule |
|---|---|---|
| Search users / status filter | Finds enabled or disabled portal accounts | Confirm the username and display name together |
| Enable | Allows that user to sign in again | Use only after access is approved |
| Disable | Blocks new sign-ins while retaining audit history | Confirm the person and reason before disabling |
| Create user | Adds a new portal account | Use a unique username and provide the password securely |
| Save user | Updates username or display name | Avoid changing usernames casually because they identify audit actions |
| Set up / disable 2FA | Changes authenticator protection for the selected account | Never copy a setup key or current code into tickets or chat |
| Reset password | Replaces the selected user's password | Confirm the selected user twice and use the approved handover method |
| Sessions | Shows where the selected account is signed in | Revoke unfamiliar sessions according to your access process |
Topic 12 of 13
#Logs: filters and evidence
| Area | What it contains | What to capture |
|---|---|---|
| Operator actions | Actions requested through the interface | Time, operator, target and outcome |
| Operational logs | General BrightBridge service events | The small time window around the symptom |
| Sync access | Player requests for served content | Player identifier, response and time |
| System warnings | Conditions needing attention | Exact warning text and whether it persists after one refresh |
| Refresh logs | Loads the latest available entries | Use once after reproducing or observing the issue |
Build a short timeline rather than copying the whole page: what was attempted, when it started, what target was involved, what BrightBridge reported and what the screen actually did.
Topic 13 of 13
#Advanced / System: what operators should know
Advanced / System changes platform-wide behaviour. Most operators only need to recognise pending changes and know when to stop.
| Control group | Why it exists | Operator boundary |
|---|---|---|
| Pending and unsaved changes | Shows edits waiting to be saved or applied | Identify the owner; do not apply unknown edits |
| Save pending | Stores reviewed edits without activating all of them | Use only as part of an approved configuration procedure |
| Save + apply changes | Activates reviewed platform settings | Treat as a change-window action with verification |
| Discard unsaved edits | Removes edits not yet saved | Do not discard another person's work |
| Roll back configuration | Restores an earlier platform configuration | Use only with platform-owner approval |
| Service reload controls | Reload supporting services after approved changes | Do not use as a general troubleshooting refresh |
| Expandable settings groups | Contain hosting, access and remote-tool configuration | Leave unchanged unless the runbook specifically names the field and value |
| Debug tools | Expose technical tests for maintainers | Operators should use the normal Players, Logs and Utility Tools paths instead |