# Web Client

## About Menu and Feature Filtering

| You can use the client filtering capability to make features and functionality unavailable in specific clients, either temporarily or permanently. Agile e6 provides the following filtering techniques: Menu filtering – lets you deactivate a menu item for one or more clients Module and feature filtering – lets you deactivate a module or individual feature for one or more clients Examples of tasks you can accomplish through client filtering include: Creating a stratification of user classes – Suppose you want to give power users access to a high level of functionality in the PC Client and limit novice users to a lower level of functionality in the Web Client. You can do this by building a common set of functionality and then filtering selected functions and features for the Web Client. Limiting availability of a feature until it's ready in a specific client – After you have have implemented a feature, you might want to roll it out in the Windows Client before you're ready to make it available in the other clients. To accomplish this, you can temporarily filter the feature for the Web Client and UNIX Client.
| Certain features are filtered out of the Web Client by default. These features were not qualified for this release of Agile e6 and Agile does not officially support them. It is strongly recommended that you do not use client filtering techniques to activate unsupported features, because doing so may produce unexpected results.