Team access for sanctions screening

Give your team the access they need.

Give analysts, developers, and administrators the access they need. Work in one team workspace, with separate permissions for people and API keys. Keep account settings, screening, and review in the right hands.

Paid plans start at $59/month for 5,000 checks each month. API and review dashboard included. See pricing.

Start freeTry the interactive demo
250 free live screenings. One lifetime allowance. No credit card required.
SanctionsKitIllustrative workflow

One organization. Defined access.

AdministratorsManage the workspace
AnalystsInvestigate and review
DevelopersConnect the API
ViewersRead permitted evidence
Human roles and API scopes stay separate.
The right access for each role

What this helps your team do

Give each person a clear role.

Defined roles for everyday work

Choose who can manage the account, connect your app, review matches, or read saved results.

Separate access for integrations

Give each integration its own key and only the scopes it needs. Keep sandbox keys separate from production keys.

A shared place for the evidence

Change access when a person’s work changes. Replace and revoke API keys when needed, and remove access when it ends.

A practical use case

Engineering builds the connection while compliance owns the review.

An engineer connects the API while an analyst reviews possible matches. Both use the same team workspace, but they need different access to do their work.

  1. 01

    Set up the organization

    An owner or admin sets up the team and gives each person a role for their work.

  2. 02

    Give the integration its own key

    Create a key for the right organization and environment. Copy its secret once into secure server settings.

  3. 03

    Review and change access over time

    Review roles as duties change. To rotate a key, create a replacement, update the integration, then revoke the old key.

Match access to each person’s task

A screening team may include an analyst, a second reviewer, a developer, and an account administrator. Start with the work each person needs to do. The analyst compares match evidence. A second reviewer approves a decision when required. The developer connects the API. The administrator manages the workspace.

Server-side checks enforce these permissions. A hidden button is not the access control. Screenings, cases, keys, files, batches, and monitors belong to an organization. An API key can perform its permitted machine operations, but it cannot act as a signed-in human reviewer.

Test access as part of your evaluation

Use invented evidence to test a full handoff. Have one person prepare a review and another eligible person perform the approval your policy calls for. Check that a developer’s key can reach only the resources its scopes allow. Keep sandbox and production access separate while you test.

Compare plan limits with the people who need seats and the integrations that need production keys. Budget completed checks, monitor capacity, and file storage too. Review access when someone changes roles or leaves. Contact the team about a specific identity need before you choose a plan.

Exercise the reviewer and approver roles

Try separate test accounts for a reviewer and an approver. Check who can review cases, approve decisions, manage API keys and read saved evidence. If your rules call for a second person to approve, the first reviewer cannot do it alone. Read the team governance guide. Set which sources to check and how long to keep records for each task.

TRY IT WITH YOUR TEAM

See if SanctionsKit fits your team.

Check your sources, try a free live check and estimate your monthly cost.

Business team meeting around a conference table with laptops
Editorial photograph · Christina @ wocintechchat.com M / Unsplash

Evaluate the details

Teams and access: practical questions.

Authentication and API credentialsSecurity and access boundariesCompare team screening plans

Explore your team’s workflow

Are human roles the same as API scopes?

No. Roles control what signed-in people can do. API scopes control permitted machine operations for a key. Adding a scope to a key does not give it a human role or permission to approve a case.

Can an API key act as a sanctions reviewer?

No. A signed-in person with the right role must review cases, publish policies, and manage the team. API keys let apps do only the tasks listed for each key’s scope.

How do we choose a plan for a team?

Count the people who need membership and the integrations that need production keys. Then estimate completed screenings, monitors, and file storage. Every paid plan includes the API and dashboard; their production checks share one allowance.

Can several teams work from the same screening history?

People in the same organization can use the saved results their roles permit them to access. Give each person the access needed for their task. A shared history helps the engineer and reviewer find the same check without sharing a secret API key.

How should we rotate an API key?

Create a new key with the scopes the integration needs. Put it in secure server settings and update the integration. Revoke the old key once the replacement is in use. Never put secret keys in browser code or logs.

Is enterprise SSO included?

Enterprise SSO is not a standard advertised feature. Contact the team about a specific identity or sign-in requirement before treating it as part of your purchase.

See SanctionsKit in action

Start free and bring your team into one workspace.

Start with 250 free live checks. Use the API or dashboard to review matches and save decisions. Choose a paid plan when you need more checks.

Start freeTry the demo Compare plans
250 free live screenings. One lifetime allowance. No credit card required.