> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/weka-filesystems-and-object-stores/quota-management/manage-quotas-using-the-gui.md).

# Manage quotas using the GUI

Configure, view, update, and remove directory quotas and default quotas using the GUI.

## Set default directory quota

A default directory quota automatically applies quota limits to every new subdirectory created under a specified parent directory. It does not apply retroactively to existing subdirectories. Use it when new directories inherit consistent limits by default, such as user home directories or project folders.

{% hint style="info" %}
Creating a default directory quota is a CLI operation. Once created, you can view, update, and remove it from the **Default Directory Quotas** tab. See [Manage quotas using the CLI](/weka-filesystems-and-object-stores/quota-management/quota-management.md).
{% endhint %}

## Set directory quota

The tenant admin can set a quota on a directory, which triggers a background task to calculate the current usage. Once this calculation is finished, the quota takes effect.

**Before you begin**

* To apply a quota to a directory, ensure there is a mount point for the relevant filesystem.
* Configure at least one Data Services container before setting a directory quota. The **Create Quota** button is not available until a Data Services container is active. See [Set up a Data Services container for background tasks](/operation-guide/set-up-a-data-services-container-for-background-tasks.md).

**Procedure**

1. From the menu, select **Manage > Directory Quotas**.
2. Select **Directory Quotas**.
3. Select the filesystem the directory quota applies to.
4. In the Create Quota dialog, set the following:
   * **Directory Path:** The full path to the directory quota to be set on.
   * **Hard Quota Limit:** The hard quota limit defines the maximum used capacity above the soft quota limit, which prevents writing to the directory.
   * **Soft Quota Limit:** The soft quota limit defines the maximum used capacity that triggers a grace period timer. Data can be written to the directory until the grace period ends or the hard quota limit is reached.
   * **Owner:** The directory’s owner, such as user name, email, or slack ID (up to 48 characters).
   * **Grace Period:** When the soft quota limit is reached, a grace period starts. After this period, data cannot be written to the directory.\
     The system sets the directory quota in the background.
5. Select **Submit**.
6. To monitor the directory quota setting background task, select **Monitor > Background Tasks.**

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-a3db9820e777093c30e231a5c9e74c7eb8301b71%2FDirectoryQuotaSetting.png?alt=media" alt=""><figcaption><p>Set a directory quota</p></figcaption></figure></div>

## View directory quotas and default quota

You can view existing directory quotas and the default quota that are already set.

**Procedure**

1. From the menu, select **Manage > Directory Quotas**.
2. Select the relevant tab: **Directory Quotas** or **Default Directory Quotas**.
3. Select the filesystem in which the directory quotas are already set.
4. On the **Directory Quotas** tab, to view all quotas or only the exceeding quotas, select the **Exceeding quotas/All quotas** switch.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-58490ec9ee7585ad6667d6d30b82f2180ac6a4ea%2Fview_all_dir_quotas.png?alt=media" alt=""><figcaption><p>View directory quotas</p></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-88e5a176fb6caa2d6bb85e281cdcefa3d49661b3%2Fview_default_dir_quotas.png?alt=media" alt=""><figcaption><p>View default directory quotas</p></figcaption></figure></div>

## Update a directory quota or default quota

You can update an existing directory quota or default directory quota. Updating a default quota applies only to new directories.

**Procedure**

1. From the menu, select **Manage > Directory Quotas**.
2. Select the relevant tab: **Directory Quotas** or **Default Directory Quotas**.
3. Select the filesystem in which the quotas are set.
4. Select the three dots on the right of the required quota. From the menu, select **Update**.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-a2a29ddc1fd277f221f53a7a5fb45be46470b884%2Fupdate_dir_quota_menu.png?alt=media" alt=""><figcaption><p>Update a directory quota</p></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-364333ac881cb4a49973fa0f3f205c07e9994666%2Fdefault_dir_quota_menu.png?alt=media" alt=""><figcaption><p>Update a default directory quota</p></figcaption></figure></div>

5. In the Quota Settings Update dialog, modify the following settings according to your needs:
   * **Hard Quota Limit:** The hard quota limit defines the maximum used capacity above the soft quota limit, which prevents writing to the directory.
   * **Soft Quota Limit:** The soft quota limit defines the maximum used capacity that triggers a grace period timer. Data can be written to the directory until the grace period ends or the hard quota limit is reached.
   * **Owner:** The directory’s owner, such as user name, email, or slack ID (up to 48 characters).
   * **Grace Period:** When the soft quota limit is reached, a grace period starts. After this period, data cannot be written to the directory.
6. Select **Submit**.

<div align="center" data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-dde92b21be16894e998edd9257ec07b8fdf1710d%2Fupdate_quota.png?alt=media" alt=""><figcaption><p>Quota Settings Update</p></figcaption></figure></div>

## Remove a directory quota

You can remove (unset) a directory quota if it is no longer required.

**Procedure**

1. From the menu, select **Manage > Directory Quotas**.
2. Select the **Directory Quotas** tab.
3. Select the filesystem in which the directory quota is set.
4. Select the three dots on the right of the required directory quota. From the menu, select **Remove**.
5. In the Quota Deletion message, select **Yes**.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-5acee433ded05672394057912b99388701cbbedd%2Fremove_quota.png?alt=media" alt=""><figcaption><p>Remove a directory quota</p></figcaption></figure></div>

## Remove the default quota for new directories

You can remove (unset) the default quota settings for new directories created in a specific filesystem. The quota of existing directories is not affected.

**Procedure**

1. From the menu, select **Manage > Directory Quotas**.
2. Select the **Default Directory Quotas** tab.
3. Select the filesystem in which the default quotas are already set.
4. Select the three dots on the right of the required default quota. From the menu, select **Remove**.
5. In the Default Quota Deletion message, select **Yes**.

## Set a user or group quota

A user or group quota limits the capacity a specific POSIX user or group can consume across the filesystem, wherever that data sits in the directory tree. Unlike a directory quota, it is not bound to a path.

**Before you begin**

* Enable user quota accounting on the filesystem. This is a CLI operation. See [Manage quotas using the CLI](/weka-filesystems-and-object-stores/quota-management/quota-management.md).
* Configure at least one Data Services container. See [Set up a Data Services container for background tasks](/operation-guide/set-up-a-data-services-container-for-background-tasks.md).

**Procedure**

1. From the menu, select **Manage > Directory Quotas**.
2. Select the **User & Group Quotas** tab.
3. Select the filesystem the quota applies to.
4. Select **Create Quota**.
5. In the **Create Quota** dialog, set the following:
   * **Type:** Select **User** or **Group**.
   * **User ID:** The numeric POSIX ID of the user the quota applies to. For a group quota, specify the group ID.
   * **Hard Quota Limit:** The maximum capacity the user or group can use. Writes are blocked when this limit is reached.
   * **Soft Quota Limit:** The capacity threshold that starts the grace period timer. Writes are allowed until the grace period expires or the hard quota limit is reached.
   * **Grace Period:** The time allowed after the soft quota limit is reached before writes are blocked.
6. Select **Submit**.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-37f38b97092de3dfa964bf5a84594f4988d5807b%2Fcreate_user_quota.png?alt=media" alt=""><figcaption><p>Set a user quota</p></figcaption></figure></div>

## View user and group quotas

You can view the user and group quotas set on a filesystem, along with the capacity each user or group currently consumes.

**Procedure**

1. From the menu, select **Manage > Directory Quotas**.
2. Select the **User & Group Quotas** tab.
3. Select the filesystem in which the quotas are already set.
4. To view all quotas or only the exceeding quotas, select the **Exceeding quotas/All quotas** switch.

The table lists each quota by **ID** and **Type** (User or Group), with its used capacity, soft and hard limits, usage, grace period, and the time it has been exceeding the soft quota.

<div data-with-frame="true"><figure><img src="https://2924606337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqDcZwR9zamxPsY03oTOq%2Fuploads%2Fgit-blob-eeb02e5b26afdfd2c8730fd1f9d168d9ab9b906e%2Fview_user_and_group_quotas.png?alt=media" alt=""><figcaption><p>View user and group quotas</p></figcaption></figure></div>


---

# 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.weka.io/weka-filesystems-and-object-stores/quota-management/manage-quotas-using-the-gui.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.