# Manage filesystem groups

A filesystem group functions as a policy engine for tiered storage, enforcing consistent data lifecycle rules across multiple filesystems. By grouping filesystems, you centrally manage how data transitions between the high-performance SSD tier and the object store.

**Lifecycle policy enforcement:** The filesystem group serves as the centralized configuration point for the tiering cue and the drive retention period. These settings dictate the timing for copying data to the object store and releasing it from the SSD cache. Any change to a group's configuration immediately applies the updated lifecycle policies to all its member filesystems.

**Association requirements:** To enable tiering, every filesystem must be associated with a filesystem group. The WEKA system supports up to eight distinct filesystem groups, allowing you to define and maintain separate tiering strategies for different workload types within the same cluster.

**Related topics**

[Manage data lifecycle for tiered systems](/5.0/weka-filesystems-and-object-stores/tiering.md)


---

# Agent Instructions: 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:

```
GET https://docs.weka.io/5.0/weka-filesystems-and-object-stores/managing-filesystem-groups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.