# How do you filter by multiple users in Adalo?

Filter Adalo records connected to several users by choosing the right relationship shape, applying Contains and AND/OR rules, and testing known sample data.

- Canonical URL: https://adalocado.com/answers/multiple-user-filters
- Verification: Verified from current public evidence
- Topic: Lists, Filters, and Search
- Skill level: Advanced
- Last reviewed: 2026-08-16
- Index status: index-now

## Short answer

Model the user-to-record connection first, then filter the list using relationship Contains rules and explicit AND/OR behavior. Many-to-many comparisons have platform limitations, so test the exact relationship shape.

Write the intended set rule in plain language before configuring filters: match any selected user, every selected user, or the logged-in user plus another condition. Model that relationship explicitly and test records that differ by only one membership. Current Adalo documentation limits logical relationship comparison to one-to-many shapes, so a join collection often makes roles, dates, and queries clearer than a dense many-to-many relationship. Protect the records with Collection Permissions; the list filter only shapes what the component displays.

## Intended outcome

A filtered list whose rules clearly express which user relationships qualify.

## Requirements

- Defined relationship cardinality
- List of records
- Representative multi-user test data

## Step by step

1. **Write the rule in plain language**

   Decide whether records must contain all selected users, any selected user, or one current user.

2. **Inspect relationship shape**

   Confirm whether the record has one user, many users, or a join collection.

3. **Add filters independently**

   Prove each Contains or relationship rule before joining filters with AND/OR.

4. **Test overlaps**

   Use records connected to neither, one, and multiple users.

## Why it works

- Filter operators compare the current record’s relationship to selected user records.
- Current Adalo documentation limits logical relationship comparisons to one-to-many shapes; comparing many records with many records needs a different model.
- Collection Permissions are the authorization layer. A Logged-in User list filter alone must not be treated as data security.

## Data model

| Collection | Properties | Relationships |
| --- | --- | --- |
| Users | Name, Role | Has many memberships |
| Records | Name, Status | Has many memberships |
| Memberships | Role, Joined Date | Joins one user to one record |

## Common failures

### A many-to-many comparison is unavailable

Use a join collection or reshape the query around a one-to-many relationship.

### The filter looks correct but data is exposed

Configure Some Logged In Users collection permissions through the required User relationship; do not rely on component filtering for access control.

## Testing checklist

- [ ] A record related to only the first selected user appears under an OR rule.
- [ ] A record missing one selected user is excluded under an AND requirement.
- [ ] No selected users produces the deliberately chosen default result set.
- [ ] Two logged-in users can access only the records allowed by Collection Permissions.
- [ ] AND/OR matches the written rule
- [ ] Overlap cases are tested
- [ ] Empty selection behavior is intentional
- [ ] Two users prove the permission boundary

## Limitations

- Many-to-many comparisons can be difficult to express and must be tested with the exact relationship shape.
- A component filter is not an authorization boundary; private records require Collection Permissions.

## Community evidence

### [From Structure to Connections](https://forum.adalo.com/t/from-structure-to-connections-setting-up-effective-relationships-in-adalo/59952)

The discussion recommends intermediary join records for flexible many-to-many cases and explains that metadata such as role or joined date belongs on that record. Boundary: These are practitioner recommendations; the exact AND or OR expression still depends on the available data context and must be tested with representative records.

## Sources

- [Adalo relationships](https://help.adalo.com/database/relationships)
- [Adalo filtering](https://help.adalo.com/component-basics/conditions-and-filtering/filtering-in-adalo)
- [Adalo join collections](https://help.adalo.com/database/relationships/adalo-join-collections)
- [Adalo collection permissions](https://help.adalo.com/database/collection-permissions)
- [Adalo forum: relationship structure](https://forum.adalo.com/t/from-structure-to-connections-setting-up-effective-relationships-in-adalo/59952)

Markdown version: https://adalocado.com/answers/multiple-user-filters.md