> For the complete documentation index, see [llms.txt](https://help.screena.ai/resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.screena.ai/resources/faq/personalization/to-which-extent-are-the-screening-thresholds-adjustable.md).

# To which extent are the screening thresholds adjustable?

The core feature of a screening solution like Screena is to match and search named entities across 2 or more data objects – at least one being the **source** and another the **target** of the match query.

Simply put, it means customer attributes shall be matched against list elements in the context of customer screening. Likewise, fields (i.e., business elements) within transactions shall be matched against list elements in the context of transaction screening.

<figure><img src="/files/KjKzwDBru0hjjIylDC8I" alt=""><figcaption><p>Match Query Object Model</p></figcaption></figure>

When posting a request to Screena API, it is possible to **append multiple match queries** with different settings, including thresholds and [matching algorithms](https://developer.screena.ai/#algorithms).&#x20;

Screena's flexible way of building and combining match queries makes it easy to adjust screening parameters with all needed granularity – per list, request, or business element within transactions.

Here is a code sample showing how to set up distinct thresholds per list:

{% code lineNumbers="true" %}

```json
{
	"queries": [{
			"sourceData": [{
				"names": [{
					"fullName": "Abu Hassan"
				}]
			}],
			"targetData": [{
				"datasets": [{
					"label": "USA"
				}]
			}],
			"threshold": 0.95
		},
		{
			"sourceData": [{
				"names": [{
					"fullName": "Abu Hassan"
				}]
			}],
			"targetData": [{
				"datasets": [{
					"label": "UN"
				}]
			}],
			"threshold": 0.9
		}
	]
}
```

{% endcode %}