Current Behavior:
In a Revu Studio Session, the Session Host has access to information and controls that are not available to other Session participants, including visibility into which invited users have joined or have not yet joined the Session.
This creates a single point of dependency on the primary Session Host. If the Host leaves, is unavailable, or is not actively monitoring the Session, other members of the project team cannot access the same information or perform certain Host functions.
Requested Improvement:
Add the ability for a Session Host to designate one or more Co-Hosts with the same or a configurable subset of the Host's permissions and abilities.
A Co-Host should be able to perform key Session management functions such as:
- View which invited users have joined or have not joined the Session.
- Add or manage Session participants.
- Monitor Session activity and reviewer participation.
- Track review progress and usage.
- Assist with Session management when the primary Host is unavailable.
The primary Host should retain the ability to assign or remove Co-Host permissions.
Why This Would Be Valuable:
Many organizations use Revu Studio Sessions as part of team-based workflows where multiple people are responsible for coordinating and monitoring the same review. Requiring one individual to remain the sole Host can create an unnecessary bottleneck.
For example, our team uses Studio Sessions to coordinate plan reviews involving multiple reviewers. A project coordinator may create and manage the Session, while project managers or other designated team members may also need to monitor participation, add reviewers, or track progress. If the primary Host is unavailable, the team should not lose access to these management capabilities.
A Co-Host function would provide greater flexibility, continuity, and accountability while still allowing the primary Host to control who receives elevated permissions.
Suggested Functionality:
Consider adding a "Co-Host" role for Studio Sessions that provides the same or configurable Host-level permissions. This would allow organizations to assign responsibility to multiple team members while maintaining appropriate control over the Session.
This would be particularly useful for projects where Session management needs to continue when the primary Host is unavailable or when project managers need visibility into participation and progress.
