> 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 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/viewing-a-collaborators-hardware-metrics.md?ask=<question>&goal=<endgoal>
```

`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.