RiskOS™ Dashboard Setup

Learn how to set up Watchlist in RiskOS™ to screen and monitor entities

Set up Watchlist in the RiskOS™ Dashboard

Before you start

Make sure you have the following:

Access to the RiskOS™ Dashboard with the Watchlist enrichment enabled.
  • Your account owner or administrator can enable this for you. If you're unsure who to contact, reach out to support for assistance.

A basic understanding of RiskOS™ workflows and components.
  • If this is your first time working with workflows, review the Workflow overview to understand inputs, enrichments, routing logic, and decisions.


How it works

Socure Watchlist evaluates individuals and entities against global sanctions, PEP registries, enforcement lists, and adverse media to support compliance and risk management.

Watchlist screens individuals and businesses, continuously monitors for updates, and generates alerts to help your compliance team manage risk efficiently.

Watchlist returns:

  • Screening Results: Real-time identification of potential matches against global lists.
  • Monitoring Alerts: Continuous tracking of entities to notify you of profile changes or new hits.
  • Correlation Scores: Insights into Name Match and Entity Correlation to help reduce false positives.

How Watchlist fits into a workflow

In RiskOS™, workflows are built by connecting reusable components. Watchlist is added as an Enrichment step.

Once the enrichment runs, its outputs are available to downstream workflow components, such as:

  • Conditions
  • Decision rules
  • Rule score cards
  • Manual review steps
  • Final decisions

Execution flow in RiskOS™

Watchlist runs synchronously as part of a RiskOS™ workflow. There is no user handoff or pause in execution.

flowchart LR
    A[Input]
    B[Watchlist]
    C[Routing logic]
    D[Decision]

    A --> B --> C --> D
  1. Input: You call the Evaluation API with identity data (Name, DOB, National ID) and a Bearer token for authentication.
  2. Watchlist enrichment: RiskOS™ screens the identity against configured global policies.
  3. Routing logic: The workflow evaluates match scores, entity correlation, and reason codes.
  4. Decision: The workflow returns a final outcome (for example, Accept, Review, or Reject).

Workflow components used by Watchlist

ComponentPurposeTypical inputOutput / What to use next
InputStart an evaluationIdentity data (Name, DOB, SSN)Workflow execution begins
EnrichmentScreen against listsMatch signals, list details, reason codes
ConditionBranch based on riskName Match/Correlation scoresRoute to appropriate path
DecisionEmit final outcomeRouted valueAccept / Review / Reject

Configure Watchlist

1. Set up access and policies

Before building your workflow, ensure your environment is ready:

  • API Access: Access your keys and sample requests on the Developer Workbench.
  • Permissions: Verify you have an Administrator, Case Officer, Case Supervisor, or Case Analyst role.
  • Configure Policies: Set thresholds for Name Match, Entity Correlation, and DOB match tolerance. Define PEP filters and suppression rules.

2. Add Watchlist to a workflow

  1. In the RiskOS™ Dashboard, go to Workflows and create a new workflow or open an existing one.
  2. On the workflow canvas, select the plus (+) icon.
  3. Add an Enrichment step and select Watchlist.

3. Enable monitoring and portfolio import

  • Enable Monitoring: Register a webhook to track updates in real time.
  • Import Portfolio: Use the Batch Jobs CSV upload to import active customers. Mark initial matches as false positives to establish a clean monitoring baseline.

4. Save and publish

Test your workflow in Sandbox before publishing. Only live workflows process API evaluations.



Workflow testing checklist

Use this checklist to confirm accuracy, resilience, and completeness before going live.

Integration & Policy:

API keys authenticated and requests signed correctly.
Policies configured with thresholds aligned to risk tolerance.
Customer portfolio imported successfully (if applicable).
Workflow & Routing:

Workflow published with Watchlist enrichment added.
Identity inputs (name, date of birth, national ID) are collected and passed consistently.
Review or fallback paths (Case Management queues) are clearly defined.
Operational readiness:

Monitoring enabled and webhook/email alerts tested.
Alerts reviewed and dispositioning feedback loop validated.