Filtering by Field Values in Role Assignments

Configuration Scope: Exportable

This setting is included in configuration exports and will be the same across all environments once the config file is imported.

When you add or edit a Role Assignment you can limit its scope to records whose fields meet specific conditions. These conditions are defined in the Field Values filter.

Three comparison types are supported:

Comparison	Symbol in filter string	Works with	What it does	Example
Equals	=	Single-value text, number, choice, boolean, date, taxonomy	True when the field’s value exactly matches the value you supply.	{ "RecordStatus":"=Approved" }
Contains	~	Text fields, multi-value taxonomy, multi-choice, multi-person	True when the supplied value occurs inside the field value. For strings it’s a substring match; for arrays/taxonomy it matches if any element equals the supplied value.	• String: { "Title":"~urgent" } • Taxonomy: { "Tags":"~Finance" }
In	@	Same types as Equals	True when the field’s value equals one of a semicolon-delimited list of values you supply.	{ "Priority":"@High;Medium" }

Behaviour details

1. Case sensitivity – Matches are case-sensitive (Finance ≠ finance).
2. Boolean fields – Use the literal true or false with Equals only, e.g. "IsArchived" equals "false".
3. Multi-value taxonomy / choice
   • Contains succeeds if any selected term equals the test value.
   • In succeeds if the selected value appears in the candidate list.
4. Multiple field filters – When you specify several filters, the rule uses AND logic: every filter must pass for the Role Assignment to apply.

Quick reference cheatsheet

=   Exact match          Title "=Final Report"
~   Contains / member    Title "~report"     Tags "~Finance"
@   In list (;)          Priority "@High;Medium"