> ## Documentation Index > Fetch the complete documentation index at: https://support.duna.com/llms.txt > Use this file to discover all available pages before exploring further. # Screening and monitoring Screening checks people and businesses associated with a [Connection](https://support.duna.com/connections.md) for sanctions, politically exposed person (PEP) status, adverse media, and regulatory enforcement. Monitoring repeats screening throughout the relationship with the Connection. A **hit** is a possible match between a screened person or business and a profile returned by a screening provider. Every hit opens an [investigation](https://support.duna.com/investigations.md) for an analyst to assess. Duna sends the details collected about each person and business during onboarding and review to third-party screening providers, which run the checks and return the results. Your configuration specifies which providers your organization uses and which businesses and people are screened. > [!NOTE] > > **Admins**, **Reviewers**, **Task Reviewers** and **Members** can see screening results. **Admins**, **Reviewers** and **Task Reviewers** can assess them. See [Roles](https://support.duna.com/roles.md#investigations). ## Screening Screening runs when the business submits its onboarding, and again when its details change: a resubmission after a [Follow-up](https://support.duna.com/follow-ups.md), a new owner, a corrected date of birth. A screening without hits requires no action from you. If there is a hit, assess it in an investigation. ### Add a person or business to be screened To screen a person or business that wasn't declared during onboarding: 1. Open the [review](https://support.duna.com/managing-reviews.md). 2. Go to **Associated entities** and click **Add associated entity**. 3. Choose **Person** or **Business**. 4. Select their relationship to the Connection, such as ultimate beneficial owner (UBO), representative, or signatory, and enter their details. 5. The new entity starts as **Not published**. Click **Publish entity** to include it in the Connection's configured checks, including screening and monitoring. Click **Unpublish entity** to remove it from those checks. ## Monitoring Monitoring starts with the first screening for each screened person or business. The lists are checked again about once a day. A new match opens an investigation like any other hit. See [What a hit changes](#what-a-hit-changes) for its effect on the Connection. New monitoring hits do not trigger email notifications. Use the **Investigations** section to find and assess them. Monitoring stops when the Connection is rejected or terminated. A person or business that is no longer part of the Connection, for example an owner who left, is no longer monitored either. ## Find investigations Open **Investigations** in the Dashboard sidebar. Use **Inbox** for unassigned open investigations, or **My open investigations** for those assigned to you. The **Screening** view shows open investigations for Connections with a review in progress. The **Monitoring** view shows those for Connections without a review in progress. Inside a review, the **Screen** step shows investigations for that Connection. See [Investigations](https://support.duna.com/investigations.md) for how to assess a hit and finalize the outcome. ## What a hit changes A hit opens an investigation. It does not automatically change the Connection's risk score or capabilities. > [!NOTE] > > During a review, the Connection can't be accepted while it has an open investigation. Declining is always possible. When an analyst finalizes the investigation, the outcome determines what happens next: * **False positive**: It does not affect the Connection's risk score or capabilities. * **True positive with no relevant finding**: It does not affect the Connection's risk score or capabilities. * **True positive with a relevant finding**: the finding contributes to the Connection's risk score according to your policies. A review opens automatically, unless the Connection already has an open onboarding or review. The analyst uses the review to decide on the Connection's capabilities. ## For auditors [Due Diligence Files](https://support.duna.com/due-diligence-files.md) include a Screening report and an Investigations report. The Screening report lists every person and business screened, each screening run with its date and the provider settings used, and when monitoring started and stopped. The Investigations report lists every hit with the analyst's assessment, their notes and the outcome. ## FAQ > [accordion] Can I change which lists are searched or how closely a name must match? > > Not from the Dashboard. Lists, providers and match sensitivity are part of your configuration: talk to your account manager at Duna. > [accordion] Can I run a screening on demand? > > Available on request. Your developers can trigger a screening through the API (`request-screening` action on a Connection), read a summary of open and relevant findings, and subscribe to webhooks when an investigation opens or is finalized. See the [API documentation](https://docs.duna.com). > [accordion] Why does an older review show tasks like “Suspected sanction hit”? > > Before the Investigations section existed, hits were tasks inside the review. Hits from that time stay where they were; new hits open as investigations. > [accordion] Why does one hit come with a report and no profile details? > > Some providers have their own analysts check potential matches first and only pass on confirmed ones. Those hits show **View report** instead of a matched profile. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.