> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/collaborators/what-is-a-collaborator.md). # What is a Collaborator? In the Rhino FCP, collaboration is set up around workgroups. Each workgroup has a lead and several members. To add collaborators to projects, you simply add their workgroups. This method helps keep collaboration straightforward and maintains controlled access. ### Collaborative Workgroups and Workgroup Leads Workgroups are the foundational units of collaboration in the Rhino 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 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** 1. **Workgroup Name:** The name of the collaborating workgroup. A workgroup is usually a lab or smaller team that is part of a larger organization. 2. **Workgroup Lead:** The person who is leading the workgroup. The workgroup lead must approve all Collaboration requests 3. **Site Name:** The name of the site where the remote data will live 4. **Number of Members:** The number of team members at a site, inclusive of the Workgroup Lead 5. **CPU Usage:** The CPU usage at a specific Rhino Client 6. **Storage Usage:** The disk storage usage at a specific Rhino Client 7. **Memory Usage:** The memory (RAM) usage at a specific Rhino Client 8. **GPU Usage:** Where applicable, the GPU usage at a specific Rhino Client. Not all Rhino Clients are required to have GPUs attached 9. **VRAM Utilization:** Where applicable, the VRAM utilization at a specific Rhino Client. Not all Rhino Clients are required to have GPUs attached 10. **UUID:** The unique identifier for a specific Code Object version within the Rhino FCP 11. **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?](/secure-access/what-is-secure-access.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.rhinofcp.com/collaborators/what-is-a-collaborator.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.