Softr Docs
List Conditional Filters
The List conditional filtering feature allows you to filter the list based on the defined conditions. It's available through Conditional Filters in the List settings sidebar.
Conditional Filters
Let's see how it works. First of all, from the dropdown at the top you should choose whether any or all of the defined conditions should be met for filtering the list.
All or any of the conditions
You can add as many conditions as required, and they'll be joined with OR (match any is selected) or AND (match all is selected).
"Match all" option selected
Now, lets the see how the Condition is configured. There are three fields in Condition Settings:

1. Field

Here, you need to select a field from the specified Airtable base, for which the condition will be defined.

2. Condition

The following options are available for defining a relationship between the Field and the Value.
  • is – the Field needs to match the Value exactly
  • is not – the Field has any value apart from the Value
  • is one of –the Field is any of the Value(s) (multiple values can be added)
  • is none of – the Fields has any other value apart from the Value(s) (multiple values can be added)
  • is empty – the Field is empty
  • is not empty – the Field is simply not empty and has a certain value

3. Value

Here, you have two options. Let's consider each one separately.

Entering a specific value

You can enter a specific value for the selected field, so that only the records having that value are displayed.
If the value contains a space, you'd need to copy it from somewhere else instead of typing it in.
Let's say we have a list of employees and want to display only the ones whose position is Project Manager.
A list of employees
Below you can see how we apply a conditional filter to show only the entries that meet this condition.
Applying a conditional filter to the list

Using a Checkbox field in a Conditional Filter

Airtable has a Checkbox field type which you might want to use in a conditional filter. You can't use a checkbox field directly, but there's a workaround.
The list block doesn't have a Checkbox field type (the Table block has it though), but you can still use it in a conditional filter (if you have it on Airtable) even without displaying it.
As shown below, you need to use a formula field to convert your checkbox values to text to be able to use them in a conditional filter.
Converting the checkbox values
Now, you can use the formula field values in a conditional filter the same way you'd use any other textual values. Please, note you don't necessarily need to use "Yes" and "No" (can be replaced with anything).

Using Logged-in user's parameters

Using this option, you can set a condition to filter the list for each logged-in user personally, so that each user only sees entries related to him/her.
By default, you'll have user's Email and Email-Domain options here. However, if you've connected an Airtable users table, all the fields from that table will also become available for your choice.
Fields added from the connected Airtable base
Let's consider a specific example to make it clear how this works and in which cases it can be applied. Let's imagine you have a task list with such fields as Assignee, Description, and Status. The Assignee field contains the emails of the users to which the task is assigned.
Task list on Airtable
To be able to view their tasks, the users need to log into the system and navigate to the page with the list. However, you want each user to see only his/her tasks, and that can be achieved with a single condition. In Condition Settings we are going to set the Field to Assignee and Action to Logged in User's Email. This way the logged in user will only see those entries of the list, where the Assignee field corresponds to his/her email address. The below GIF illustrates this.
That's it. This way, you can set a condition for any of the fields in your list and filter the list accordingly for your logged in users.
More attributes will be added soon to allow for more advanced filtering based on additional user attributes such as user roles, statuses, and so on.