> 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/viewing-a-collaborators-hardware-metrics.md). # Viewing a Collaborator's Hardware Metrics How to view a hardware metrics for your collaborators. At a minimum, you will see your own Rhino Client with all your available hardware metrics. If you have multiple collaborators in your projects, and you wan to see their available hardware metrics, select Collaborator from the left side of the screen. A box for each collaborator, along with their hardware metrics appears on the screen. {% hint style="info" %} NOTE: The metrics shown on the Collaborators page are not dynamic; you will need to refresh the page for updated metrics. {% endhint %} If a collaborator is missing GPU metrics or they are not updating upon refresh of the page, please refer to [Why are GPU metrics not present or updating within the Collaborators page?](/frequently-asked-questions/frequently-asked-questions-faqs.md#other-questions) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rhinofcp.com/collaborators/viewing-a-collaborators-hardware-metrics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.