A group organizes already-working players. Fix each player first; grouping cannot repair a broken feed, incompatible file or invalid access rule.
Before you start
Two or more Web players tested independently.
A clear group purpose such as languages, camera angles or an episode list.
A default selection and shared audience policy.
Settings explained
These are the controls an operator needs to understand. Internal field names and implementation events are intentionally omitted.
Group contents
Define what the viewer may switch between.
- Group name and active state
Operator identity and lifecycle state.
- Group type
Language list, file/episode list or supported grouped experience.
- Players and display names
Ordered existing players with audience-facing labels.
- Default player
Player selected when the viewer page first opens.
Shared viewer experience
Apply the page-level audience policy.
- Authorization
Shared password or per-viewer credentials for the grouped page.
- PayPal pay-per-view
Payment gate and amount for the group.
- Logo, cover and background
Shared visual identity for the grouped experience.
- Event date, timezone and support
Scheduled access context and viewer support contact.
Safe first workflow
- 01
Open every candidate player in a clean browser and verify playback.
- 02
Create a group and choose Language or Files based on the viewer task.
- 03
Add players in the intended order, give each a clear label and select the default.
- 04
Configure one shared audience policy and branding layer.
- 05
Test the viewer URL, default selection and every switch.
Workflow examples
Multilingual conference player
Production supplies one complete feed per language.
How to build it
- 1
Create and test one player for every produced language feed.
- 2
Create a Language group and name players with audience-facing language labels.
- 3
Choose the default language and apply the shared access policy.
- 4
Test switching while every source is live.
Episode or replay library
Several verified recordings should appear in one ordered viewer page.
How to build it
- 1
Create and verify one VOD player per finalized asset.
- 2
Add them to a Files group in the intended order.
- 3
Set display labels, default item, branding and access.
- 4
Test every item and browser history/navigation behavior.
Verify the result
- The default player opens on first load.
- Every language, angle or file label selects the matching player.
- Shared authorization/payment applies consistently to the group.
Troubleshooting
One group item fails while others work
Check- Open that player outside the group.
- Check its source and active state.
- Verify the group still references the intended player.
Repair or replace the individual player; do not rebuild the entire group.