In the Rhino Health FCP, collaboration is organized on a workgroup basis. Each workgroup includes a workgroup lead and multiple workgroup members. Collaborators are added to projects by adding their workgroups. This approach streamlines collaboration and ensures controlled access.
Collaborative Workgroups and Workgroup Leads
Workgroups are the foundational units of collaboration in the Rhino Health FCP. Each workgroup is led by a designated workgroup lead, responsible for overseeing project access and permissions within the workgroup.
Enabling Controlled Collaboration
This workgroup-based approach ensures that collaboration is structured, controlled, and aligned with project goals. The workgroup lead plays a pivotal role in managing access and fostering effective teamwork.
Guided Collaboration in Action
Imagine you're launching a multi-institutional research initiative. By adding the workgroups of researchers from each institution, you establish a collaborative framework. The lead of each workgroup approves project access, facilitating seamless collaboration while maintaining control.
Summary
Collaboration in the Rhino Health FCP revolves around workgroups, each led by a lead. Adding collaborators means adding entire workgroups, streamlining access, and promoting controlled collaboration. This approach enhances project collaboration and accelerates collective insights.
Key Components of a Collaborator
Attributes
- Workgroup Name: The name of the collaborating workgroup. A workgroup is usually a lab or smaller team that is part of a larger organization.
- Workgroup Lead: The person who is leading the workgroup. The workgroup lead must approve all Collaboration requests
- Site Name: The name of the site where the remote data will live
- Number of Members: The number of team members at a site, inclusive of the Workgroup Lead
- CPU Usage: The CPU usage at a specific Rhino Client
- Storage Usage: The disk storage usage at a specific Rhino Client
- Memory Usage: The memory (RAM) usage at a specific Rhino Client
- GPU Usage: Where applicable, the GPU usage at a specific Rhino Client. Not all Rhino Clients are required to have GPUs attached
- VRAM Utilization: Where applicable, the VRAM utilization at a specific Rhino Client. Not all Rhino Clients are required to have GPUs attached
- UUID: The unique identifier for a specific Code Object version within the Rhino FCP
- Secure Access: An optional set of abilities that can be granted to a collaborator to visualize raw data, view Code Run logs, etc. For more information about Secure Access, please refer to What is Secure Access?
Actions
- Adding or Removing a Collaborator from A Project: Add or remove a Collaborator from your project
- Viewing a Collaborator's Hardware Metrics: Viewing your Rhino Client and your Collaborator's hardware usage statistics
- Viewing Your Project's Permissions: View your project's permission policies that were set when defining the project
Interfaces
Below are a series of screenshots that detail how you can interact with Collaborators within the Rhino FCP
Main Collaborators Page
The main interface for initiating the creation of a collaboration and viewing a project's permissions.
Adding a New Collaborator to Your Project
For more information about adding a new collaborator to your project, please refer to Adding or Removing a Collaborator from a Project.
Viewing Your Project's Permissions
For more information about viewing your project permissions, please refer to Viewing Your Project's Permissions.
Viewing Permission Personas Assigned to Permissions in your Project
For more information about viewing your project permissions, please refer to Viewing Your Project's Permissions.