> 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 %}


---

# 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://help.screena.ai/resources/faq/personalization/to-which-extent-are-the-screening-thresholds-adjustable.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.