> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/general/filters.md).

# Filters

This is a very powerful feature on our platform. Filtering helps you find the objects (people, things) via a way of adding parameters to your filter. This allows you to filter VERY fine-grained.

Afterwards you can use that filter for multiple things like [automating](/event/general/filters/automate.md) rewards or tags, sending [bulk emails](/event/communication/bulk-email.md) or [SMS](/event/communication/text-messages.md), exporting the data to CSV, taking [actions](/event/general/filters/actions.md) on the resulted objects, ...

## Create

Assign a filter to one of the many categories:

* [Members](/event/accreditation/attendance/members.md)
* [Associations](/event/planning/groups.md)
* Association leaders
* [Form responsibles](/event/accreditation/lists/forms.md)
* [Form attendees](/event/accreditation/lists/forms/attendees.md)
* [Form vehicles](/event/accreditation/lists/forms/vehicles.md)
* [Wristbands](/event/accreditation/wristbands.md)

{% hint style="warning" %}
Once created you will see that all of your possible objects are in the result of the new filter. This is because you **need to create parameters before the filter actually starts** doing some actual filtering.
{% endhint %}

## Parameters

Creating a new parameter will show you a menu of possibilities. Make a choice of what you want to achieve with your filter and pick it. 

<details>

<summary>Examples of parameters</summary>

* was born between dates
* has or hasn't got a valid bank account number
* has a job on at least one of these days
* double confirmation page open
* has (or hasn't) got a certain number of substations as preference
* has checked in on days
* has rewards assigned
* hasn't got tags
* has certain comment rating
* has downloaded ticket
* has signed (or not) a certain document

</details>

There are many more options to create parameters.

### AND / OR

When you created a parameter you can add another one. This time you will first have to make the choice if you would like to add an **AND** parameter or an **OR** parameter. These are logical operators.

If you pick **AND**, you tell the filter it should find the people who are in the results of parameter 1 **AND** parameter 2.

If you pick **OR**, you tell the filter it should find the people who are in the results of parameter 1 **OR** parameter 2.

{% hint style="info" %}

#### Example

The result of parameter 1 include `Sam`, `Isabelle` & `Nick`.

The result of parameter 2 include  `Tim`, `Frank` & `Nick`

* **AND**: The people who ended up in **BOTH** parameters, only `Nick` in this case.
* **OR**: The people who ended up in **AT LEAST ONE** parameter, so `Sam`, `Isabelle`, `Nick`, `Tim` and `Frank`.

You can combine many AND and OR operators with many parameters. Make it as simple or complex as you like.
{% endhint %}

{% hint style="warning" %}
For now the **maximum** amount of parameters is **15**. This is a hard limit to ensure the performance of the platform.
{% endhint %}

## Sharing

The results of the filter can be shared with people who do not have access to the filter system. This feature will generate a unique secured URL that can be shared. You have more configurable settings to limit access.

{% hint style="danger" %}
This feature is in BETA and is currently **only supported for Member and List vehicle filters**.
{% endhint %}

{% stepper %}
{% step %}
Open the member filter
{% endstep %}

{% step %}
Click on the title 'Share'
{% endstep %}

{% step %}
Click on the plus button in the upper right corner
{% endstep %}

{% step %}
Fill in all data needed & click on the save button
{% endstep %}
{% endstepper %}


---

# 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.eventication.com/event/general/filters.md?ask=<question>&goal=<endgoal>
```

`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.