Groups are the key to managing viewer access in RePro Stream. They provide a flexible way to organise your project's user base and control exactly which content each team or individual can view through Channel assignments.
What is a Group?
A Group is a collection of Users within a project. Groups sit between Channels and Users in RePro's content hierarchy, allowing you to assign viewing permissions to multiple users at once rather than managing access individually.
Content Flow: Programs → Channels → Groups → Users
Why Use Groups?
Groups make content management scalable and efficient. Instead of manually assigning Programs or Channels to each user individually, you assign Users to Groups and then assign Channels to those Groups. This approach offers several benefits:
Simplified Management Configure access once for an entire team or department rather than user-by-user.
Scalable Organisation Easily manage viewing permissions across small productions or large, multi-unit shoots.
Flexible Access Control Users can belong to multiple Groups, receiving access to different content based on their various roles.
Dynamic Adjustment Quickly add or remove users from Groups as team composition changes throughout production.
Common Group Structures
Groups can be organised to match your production's needs. Here are some typical examples:
Production Hierarchy
Producer Group: Access to all Channels (complete oversight)
Main Unit Group: Access to main unit Channels only
Second Unit Group: Access to second unit Channels only
Post Team Group: Access to edit and review Channels
Department-Based
Camera Department: Monitoring feeds from set
Editorial Team: Review and reference material
VFX Team: Specific shots and plates
Client Group: Approved content for review
Location-Based
On-Set Group: All active shooting Channels
Office Group: Selected feeds for remote monitoring
Vendor Group: Specific Channels relevant to external partners
Mixed Access
HODs Group: Department heads with broad access
Specialist Group: For example, stunt team accessing both second unit and editorial reference
Creating a Project Group
To create a new Project Group:
Click Groups in the left menu of your Project manager.
You'll see your Project name at the top with '> project groups'.
Click Create Group at the top right.
In the popup:
Select user group type - New Standard User Group or Mirror from Org User Group
(For more information on the Mirror from Org User Group option, see the 'Two Ways to Use Org Groups in Projects' section below.)
If selecting a New Standard User Group:
Select user group source - Create new empty User Group or Clone and input users from Org User Group
Enter a name (maximum 25 characters)
Add an optional description (maximum 255 characters)
Click Add to create the Group.
The Group appears in the Groups list after a confirmation popup.
The Default All Users Group
Every Project automatically includes a default "All Users" Group that contains every user in the project.
Key characteristics:
You cannot toggle users on or off in this Group
It automatically includes all project members
Designed as a quick way to allocate Programs/Channels to everyone at once
Useful for project-wide broadcasts or general access content
For more granular control, create additional custom Groups.
Adding Users to a Project Group
After creating a Group, assign users to it:
Click the Group's row to open the right side-panel.
Click Edit Group Users in the side-panel.
You'll see all Project Users listed with toggle switches.
Toggle on the users you want to add to this Group.
Click Save at the bottom of the Group Users area.
Users can belong to multiple Groups simultaneously, receiving cumulative access to all Channels assigned to those Groups.
Assigning Channels to a Project Group
For Group members to access content, assign Channels to the Group:
Click the Group's row to open the right side-panel.
Click Edit Group Channels.
You'll see all available Channels with toggle switches.
Toggle on the Channels you want this Group to access.
Click Save at the bottom.
Multiple Channels can be assigned to a single Group. Users in the Group will be able to view all Programs within those assigned Channels.
Organisation Groups (Org Groups)
For organisations running multiple projects with repetitive user structures, RePro offers Organisation Groups (configurable by the Org Admin only).
What are Org Groups? Organisation Groups allow you to create groups of Organisation Users at the Organisation level that can be made available to multiple Projects.
Benefits:
Create groups once and apply them across multiple Projects
Maintain centralised control over team composition
Streamline setup for similar production structures
Two Ways to Use Org Groups in Projects
Standard Group from Org Group
When creating a new Project Group, you can source users from an available Org Group. This creates a new standard group with the initial user allocation of the current Org Group. After creation, you can edit this Project Group's users independently. It won't automatically update if the Org Group changes.
Best for: Projects that need a standard starting team but will customise access as production progresses.
Mirror Group from Org Group
Create a Project Group that mirrors an Org Group. The Project Group's user allocation cannot be edited at the project level. It continuously follows any changes made to the Org Group.
Best for: Teams that change frequently at the organisational level where you want those changes reflected across multiple projects automatically (e.g., executive teams, engineering teams, recurring production units).
When to Use Org Groups
Use Org Groups when:
You run multiple projects with similar team structures
You have a core team that works across all projects
You need centralised control over team composition
Team membership changes frequently and needs to propagate across projects
Use Project Groups when:
Teams are unique to each project
You need complete control at the project level
Team composition is stable throughout the project
Read more about Organisation Users & Groups.
Group Settings and Features
Editing Groups
Click the Edit button on a Group's row to modify the Group name or description.
Deleting Groups
Click the trash icon to remove a Group. You'll be asked to confirm. Note that deleting a Group doesn't delete the Users — they remain in your project and can be assigned to other Groups.
Watermark Exemption
When Individual Watermarking is enabled for a project, you can exempt specific Groups from receiving watermarks. This is useful for trusted viewers like Heads of Department or executives.
To exempt a Group from watermarking:
Edit the Group settings.
Enable the Disable watermark option.
See Individual Watermarking for details.
Note: A user who is in a group with individual watermarking disabled will not receive a watermark on their player, even if they are in other groups that have watermarking enabled.
Visualising Groups
See the Project Dashboard section in Understanding Programs, Channels, Groups, and Users for how Groups connect Users to Channels visually.
When watermarking is enabled, you'll see watermark icons next to Groups on the Dashboard:
Droplet icon: Watermarking active
Crossed-out droplet: Watermarking disabled for this Group
Real-World Examples
Example 1: Reality TV Production with Rotating Crew
Scenario: Unscripted series with three simultaneous storylines, crew rotates between units weekly.
Groups Created:
"Story A Team" - Follows Story A (producers, editors, camera rotating in)
"Story B Team" - Follows Story B
"Story C Team" - Follows Story C
"All Story Producers" - Executive producers overseeing all three
"Floating Crew" - Available crew that might work any story
Channels:
Story A Cameras, Story B Cameras, Story C Cameras
Each team's Group has access to their story Channel + All Story Producers have all three
Group Management: As crew rotates:
Remove "Sarah" from Story A Team
Add "Sarah" to Story B Team
She immediately loses Story A access, gains Story B access
Benefit: One configuration change instantly shifts access. No need to reconfigure Channels or individual permissions.
Example 2: Agency Creative Review with Client Tiers
Scenario: Ad agency producing content for three different brands under same client umbrella. Different client contacts need different access levels.
Groups Created:
"Internal Creative Team" - Full access (all brands, all feeds)
"Brand A Stakeholders" - Brand A client contacts
"Brand B Stakeholders" - Brand B client contacts
"Brand C Stakeholders" - Brand C client contacts
"Client Executive" - CMO who oversees all brands
Channels:
Brand A Review, Brand B Review, Brand C Review
Each channel contains approved material only (no raw footage)
Group Assignment:
Internal Creative Team → All three brand Channels
Each brand's stakeholder group → Only their brand Channel
Client Executive → All three brand Channels
Watermark Strategy:
Internal Creative Team → Watermark disabled (trusted)
All client groups → Watermark enabled (includes user name + email)
Benefit: Clients can't cross-contaminate, viewing restricted to their brand only. CMO sees everything. Internal team works without watermark distraction.
Example 3: Post-Production with Layered Vendor Access
Scenario: Feature film in post with multiple external vendors (VFX, color, sound) needing different material.
Groups Created:
"Post Supervisors" - Internal team with complete access
"VFX Vendor" - External VFX house
"Color Vendor" - DI facility
"Sound Vendor" - Audio post house
"Director/Producer Review" - Creative stakeholders
Channels:
VFX Plates (raw green screen shots)
Color Sequences (editorial locked sequences)
Sound Elements (picture with temp audio)
Full Assembly (complete work-in-progress)
Group Mapping:
VFX Vendor → VFX Plates only
Color Vendor → Color Sequences only
Sound Vendor → Sound Elements only
Director/Producer Review → Full Assembly only (no raw elements)
Post Supervisors → ALL Channels
Benefit: Vendors only see material relevant to their work. Can't access other vendors' feeds or proprietary techniques. Director isn't overwhelmed by technical materials.
Group-Specific Best Practices
Design Groups by Function AND Access Level
Don't just group by department. Consider:
What they do: Camera, Editorial, VFX
What they need to see: Raw feeds, processed, finished only
Trust level: Internal, external vendor, client
Create groups at the intersection of these factors.
Plan for User Multi-Membership
Users should routinely be in 2-3 groups:
Their primary team group
A cross-functional oversight group
Possibly a location or project-phase group
This is normal and powerful. Don't try to force single-group-per-user.
Use Descriptive Names with Context
Poor: "Group 3", "Camera", "Clients"
Better: "Main Unit Camera Dept", "Client - Brand A Stakeholders", "VFX Vendor - Studio B"
Include enough context that the name is meaningful 6 months later.
Create Groups Proactively, Not Reactively
Don't wait until someone requests access. Set up logical groups during project setup:
Identify all teams/departments
Identify all external parties
Create groups for each before production starts
Much easier to add users to existing groups than create groups mid-production.
Leverage Default All Users Group Strategically
Use it for:
Company-wide announcements (via Cards & Notices)
Emergency access scenarios
General production updates visible to everyone
Don't use it as primary access method or you lose all granular control.
Mirror Groups vs. Standard Groups from Org Groups
Use Mirror when: Team composition changes constantly (executives joining/leaving projects)
Use Standard when: You want a starting point but will heavily customise (client list varies per project)
Document Group Watermark Settings
If using Individual Watermarking, maintain a simple reference:
Which groups have watermark exemptions
Why (internal team, HODs, etc.)
Who approved the exemption
Critical for security audits or if content leaks.
Review Group Membership Weekly on Active Productions
As productions progress:
People leave/join
Responsibilities shift
Vendors complete work
Set a calendar reminder to audit groups weekly. Remove users who shouldn't have access anymore.
Understanding Permissions
Different user roles have different permissions for managing Groups:
Project Admins: Create, edit, delete Groups
Project Managers: Create and edit Groups (cannot delete)
Standard Members: Cannot manage Groups
See Roles and Permissions for complete details.
Need Help?
For access or configuration issues, see Troubleshooting Access Issues.
For assistance with Group configuration, contact us at [email protected] or use our support chat widget in the bottom right corner.
Related Documentation
Content hierarchy:
Setup guides:
Related features: