Skip to main content

How to configure Screena

Written by Cristian Henkel

Screena is the AI agent that analyzes matches between a person and the subject of a watchlist (PEP, sanctions, blacklists). It works on your screening cases like any other analyst: it compares the data, leaves the evidence behind and writes its report. Your team makes the final call.

This article walks through the five sections you fill in to get it running.

Where to configure it

Settings > AI & Agents > Agents configuration.

That screen lists your organization's agents. To create a new one, click "Create".

If you cannot find the section, your organization does not have AI agents enabled yet. Write to Support to turn them on.

The form starts with the first section only. The other four appear once you pick the agent type, because all of them depend on it.

1. AI agent type

Pick the Screena card and give it a name.

The name is what shows up as the analyst on every case Screena works on, so make it one your team recognizes at a glance. Two agents cannot share a name.

You can create several Screena agents with different setups. One for sanctions matches and another for PEP, each with its own instructions and triggers.

If you change the agent type after filling things in, you lose the instructions, the tools and the triggers you loaded. The platform asks you to confirm first.

2. Roles and groups

Roles define what Screena can do. Groups define which resources it works on.

Both assignments are required: at least one role and at least one group. An agent with no roles has no permission to act. With no groups, it has no cases to work on.

Give it the same roles you would give an analyst doing this job. Screena never does more than its roles allow. Neither the instructions nor the tools widen that limit.

3. Instructions

Instructions give Screena context on how your organization works. They apply to this agent only. The section is optional: leave it blank and Screena runs with its default behavior.

You have two paths:

  • Instructions library. The dropdown on the top right offers ready-made instructions for Screena, in your organization's language and country. Load one and edit it.

  • Custom. Pick this option and write your own text from scratch.

The editor supports basic formatting and accepts up to 50,000 characters.

Loading an instruction from the library replaces whatever you already wrote, and you cannot undo it. The platform warns you first.

Be specific about what you expect from Screena. Set the tone and the format of the report. Add examples when they help clarify.

A few examples for Screena:

  • Discard the match when the ID number differs and the date of birth does not line up. Note in the report which data points you compared.

  • For namesakes with no additional data to confirm the match, leave the case pending review instead of closing it.

  • For matches against sanctions lists, state the list, the version date and the exact subject that produced the hit.

Two things to keep in mind:

  • These instructions add to the AI Instructions you set on each case template. Both combine when Screena works.

  • Do not write sensitive information. Any user with access to the settings can read them.

4. Tools

Tools extend what Screena can do on the cases you assigned to it. The section is optional.

Each tool is a switch. Some also ask you to choose what you enable:

  • Write report. Screena writes and saves the case report. Comes on.

  • Change case status. Screena moves the case only to the statuses you select: Open, Pending review or Closed. Comes on with Open and Pending review. Add Closed only if you want Screena closing cases without prior review.

  • Send requirements. Screena requests documentation using the requirement templates you select. Comes off.

  • Manual triggers. Screena runs the manual triggers you select during its work. Comes off.

If you turn on a tool that asks for options, you have to pick at least one. To enable none, leave the tool off.

5. Triggers

Triggers define when Screena runs automatically. This section is required: an agent with no triggers would never run, so the platform does not let you save it.

Click "Add trigger" and pick the event and the case template:

  • When a case is created. Screena starts as soon as the case opens, without waiting for someone to take it.

  • When an analyst is assigned. Screena starts once it is assigned as the case's analyst.

  • When the stage changes. It also asks for the stage. Only the active stages of the template you picked are offered.

You can load several triggers for the same agent. Each one is listed with its event and its template.

Saving

Click "Create". If you try to leave with pending changes, the platform asks you to confirm before discarding them.

Turning agents on and off, and editing them

The list shows each agent's name, roles, groups and creation date.

  • Edit: the settings icon opens the same screen you used to create it.

  • Turn off: the switch on the row stops the agent. It stops running and the row dims. You turn it back on with the same switch.

On an agent that already exists, triggers save instantly: you add, edit, turn off or delete one, and the change is applied. The name, the roles, the groups, the instructions and the tools save with the "Save" button.

If you deactivate a case stage that has a trigger pointing at it, the platform warns you first. It deletes that trigger, because a deactivated stage never changes and the agent would never run.

Worth knowing

  • Screena shows up as the analyst on every case it works on, with the same traceability as any team member.

  • Permissions win. If an instruction asks for something its roles do not cover, Screena does not do it.

  • Screena gathers evidence and recommends. The decision on the match stays with your compliance team.

Did this answer your question?