# Manage filesystems using the GUI
Using the GUI, you can perform the following actions:
* [View filesystems](#view-filesystems)
* [Create a filesystem](#create-a-filesystem)
* [Edit a filesystem](#edit-a-filesystem)
* [Delete a filesystem](#delete-a-filesystem)
## View filesystems
The filesystems are displayed on the **Filesystems** page. Each filesystem indicates the status, tiering, remote backup, encryption, SDD capacity, total capacity, filesystem group, and data reduction details.
**Procedure**
1. From the menu, select **Manage > Filesystems**.
## Create a filesystem
When deploying a WEKA system on-premises, no filesystem is initially provided. You must create the filesystem and configure its properties, including capacity, group, tiering, thin provisioning, encryption, and required authentication during mounting.
When deploying a WEKA system on a cloud platform (AWS, Azure, or GCP) using Terraform or AWS CloudFormation, the WEKA system includes a default filesystem configured to maximum capacity. If your deployment necessitates additional filesystems with varied settings, reduce the provisioned capacity of the default filesystem and create a new filesystem with the desired properties to meet your specific requirements.
**Before you begin**
* Verify that the system has free capacity.
* Verify that a filesystem group is already set.
* If tiering is required, verify that an object store bucket is set.
* If encryption is required, verify that a KMS is configured.
**Procedure**
1. From the menu, select **Manage > Filesystems**.
2. Select the **+Create** button.
3. In the **Create Filesystem** dialog, set the following:
* **Name**: Enter a descriptive label for the filesystem, limited to 32 characters and excluding slashes (`/`) or backslashes (`\`).
* **Group**: Select the filesystem group that fits your filesystem.
* **Capacity**: Enter the storage size to provision, or select **Use All** to provision all the free capacity.
Create filesystem
4. Optional: [**Tiering**](https://docs.weka.io/4.2/tiering/advanced-time-based-policies-for-data-storage-location#tiering-cue-policy).\
If tiering is required, an object store bucket is already defined, and data reduction is not enabled, select the toggle button and set the details of the object store bucket:
* **Object Store Bucket:** Select a predefined object store bucket from the list.
* **Drive Capacity**: Enter the capacity to provision on the SSD, or select **Use All** to use all free capacity.
* **Total Capacity**: Enter the total capacity of the object store bucket, including the drive capacity.
When you set tiering, you can create the filesystem from an uploaded snapshot. See the related topics below.
5. Optional: **Thin Provision**.\
If Thin Provision is required, select the toggle button, and set the minimum (guaranteed) and the maximum capacity for the thin provisioned filesystem.\
The minimum capacity must be less or equal to the available SSD capacity.\
You can set any maximum capacity, but the available capacity depends on the actual free space of the SSD capacity.\
Thin provisioning is mandatory when enabling data reduction.
6. Optional: **Data Reduction**.\
Data reduction can be enabled only on thin provision, non-tiered, and unencrypted filesystems on a cluster with a valid data reduction license (you can verify the data reduction license in the cluster settings). For more details, see the related topics below. \
To enable the Data Reduction, select the toggle button.
Data reduction
7. Optional: If **Encryption** is required and your WEKA system is deployed with a KMS, select the toggle button.
8. Optional: **Required Authentication**.\
When ON, user authentication is required when mounting to the filesystem. This option is only relevant to a filesystem created in the root organization.\
Enabling authentication is not allowed for a filesystem hosting NFS client permissions or SMB shares.\
To authenticate during mount, the user must run the `weka user login` command or use the `auth_token_path` parameter.
9. Select **Save**.
**Related topics**
[managing-filesystem-groups](https://docs.weka.io/4.2/fs/managing-filesystem-groups "mention")
[managing-object-stores](https://docs.weka.io/4.2/fs/managing-object-stores "mention")
[kms-management](https://docs.weka.io/4.2/usage/security/kms-management "mention")
[overview](https://docs.weka.io/4.2/licensing/overview "mention")
[#data-reduction](https://docs.weka.io/4.2/overview/filesystems#data-reduction "mention")
[#create-a-filesystem-from-an-uploaded-snapshot](https://docs.weka.io/4.2/snap-to-obj/snap-to-obj#create-a-filesystem-from-an-uploaded-snapshot "mention")
## Edit a filesystem
You can modify the filesystem parameters according to your demand changes over time. The parameters you can modify include filesystem name, capacity, tiering, thin provisioning, and required authentication (but not encryption).
**Procedure**
1. From the menu, select **Manage > Filesystems**.
2. Select the three dots on the right of the filesystem you want to modify, and select **Edit**.
3. In the **Edit Filesystem** dialog, modify the parameters according to your requirements. (See the parameter descriptions in the [Add a filesystem](#add-a-filesystem) topic.)
Edit a filesystem
4. Select **Save**.
## Delete a filesystem
You can delete a filesystem if its data is no longer required. Deleting a filesystem does not delete the data in the tiered object store bucket.
{% hint style="info" %}
If you must also delete the data in the tiered object store bucket, see the [Delete a filesystem](https://docs.weka.io/4.2/fs/managing-filesystems-1#delete-a-filesystem) topic in the CLI section.
{% endhint %}
**Procedure**
1. From the menu, select **Manage > Filesystems**.
2. Select the three dots on the right of the filesystem you want to delete, and select **Remove**.
3. To confirm the filesystem deletion, enter the filesystem name and select **Confirm**.
