> For the complete documentation index, see [llms.txt](https://docs.smolsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smolsoftware.com/features/overview/filters.md). # Filters The initial selection of users can be reduced further, with the Filter component. Users can be removed based on their group membership, their email domain or their product activity. Filters can be combined together to achieve your automation goals: 1. Group Membership Filter 2. Exclude Group Members 3. Filter Users by Email Domain 4. Product Activity Filter (coming soon)

*** ### Group Membership Filter This filter will only **keep users** if they are **within at least one of the selected groups**.

### Exclude Group Members This filter will **remove users** if they are **within at least one of the selected groups**.

### Filter Users by Email Domain This filter will only **keep users** if they their email domain **partly contains** or **exactly matches** what has been entered. When using the **Domain Contains** field, any users with a partial match to the email domain entered will be kept. e.g. adding **smol** would match all users with **smolsoftware.com**, **smolsoftware.com.au** and **smol.com**. When using the **Exact Domain** field, any users with an exact match to the email domain entered will be kept. e.g. adding **smolsoftware.com** would only match users with **smolsoftware.com** emails domains. When using both the **Domain Contains** field and **Exact Domain** field, the fields will be treated as **OR** when selecting users. e.g. **Domain Contains** = *gmail* **OR** **Exact Domain** = *smolsoftware.com* Use the **Exclude Mode** toggle, to exclude users with that match the domain criteria. e.g. **Exclude** + **Exact domain** = *smolsoftware.com* will remove any selected users *smolsoftware.com* email from your current selection criteria.

### Product Activity Filter (coming soon) This filter will only keep users who have access to the product selected **AND** have no recorded product activity for the number of days selected. *** ### Simple Filter Combinations Combining filters will progressively remove users from your original selection component. For example: 1. Choose '**Select Users by Email Domain**'. Configure the component users to select all users with a **.com.au** in their domain. 2. Select a filter '**Exclude Group Members**' with the group '**org-admins**'. To remove any organization admin users from the list of users. 3. Select '**Product Activity Filter**', for Confluence and set the **inactive days to 60**. 4. Select '**Add Users to Groups**' as your action, and add users into a group called '**Marked for removal**' 5. Select '**Create Live'** Only Users who have a an email address with a *.com.au* prefix + who are *not organization admins*, + who have been *inactive in confluence for 60 days or more*, will be added to the group 'Marked for removal'

### Advanced Filter Combinations After creating a simple filter combination, customers can use the workflow diagram, to navigate to a previous component, and create a new filter or action branch. Allowing for large complex rules that perform multiple actions.

Got a question? Check out our [FAQs](/features/faqs.md) or email us at --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.smolsoftware.com/features/overview/filters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.