> For the complete documentation index, see [llms.txt](https://run-ai-docs.nvidia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://run-ai-docs.nvidia.com/saas/resources/videos/how-to-allocate-gpu-resources-across-teams.md).

# How to Allocate GPU Resources Across Teams

## Resource Management Across Teams

Learn how NVIDIA Run:ai helps teams share GPU resources efficiently across departments and projects.

{% embed url="<https://www.youtube.com/watch?v=UFArO8_aAYw>" %}

{% hint style="info" %}
**Note**

This video was recorded using NVIDIA Run:ai version 2.24.18. The user interface, features, and workflows may differ in newer releases. For the latest information, refer to the current documentation.
{% endhint %}

### What You'll Learn:

* Configure quotas for departments and projects
* Set workload priorities across teams
* Allocate GPU resources fairly
* Improve cluster utilization
* Maintain governance across shared infrastructure
* Support operational flexibility for AI workloads


---

# 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://run-ai-docs.nvidia.com/saas/resources/videos/how-to-allocate-gpu-resources-across-teams.md?ask=<question>&goal=<user_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.