Using CertivantSettingsTeams & Roles

Teams & Roles

Organise your Certivant workspace into teams with data-isolation modes (strict, open, owner-only) and create custom roles with fine-grained permission bundles.

Who can do this:Org ownerOrg adminTeam ownerTeam admin— Settings management is admin/owner-only. Team managers can edit their own team.

The Teams & Roles settings showing organization privacy defaults, per-team applicant-isolation options, and the Teams / Roles & Permissions tabs.

What it does

The Teams & Roles page combines two related-but-distinct controls:

  1. Teams — sub-groups inside your organization, each with their own members, data visibility, and (optionally) their own forms.
  2. Roles & Permissions — custom roles that grant fine-grained permission bundles on top of the basic owner / admin / member.

Both live under Settings → Teams & Roles, as separate tabs.

When you need teams

If your organization is a single integrated business (one back-office, one shared workload, everyone sees everything), you don't need teams. The default behaviour — owner + admin + members all see the same applicants — works.

You need teams when you're an agency: multiple semi-independent professionals operating under one legal umbrella. Real-estate brokerage, mortgage agency, insurance shop. Each professional has their own clients and shouldn't see the others' work by default. Each one is a team_owner of their team; their assistant is a team_user.

Data isolation modes

The DataIsolationCard at the top of the Teams page is the most important setting. It has three modes:

flowchart LR
    Strict["Strict (per-user / per-team)<br/>Default for agencies"] -.-> Open
    Open["Open (everyone sees everything)<br/>Default for integrated businesses"] -.-> Strict
    Strict -.-> OwnerOnly["Owner-only<br/>For teams of independents"]
ModeWho sees what
Strict (default)Each user owns their KYC/KYB applicants. Other agents' work is hidden. Org owner + admin always see everything (so they can re-assign orphans).
OpenEvery org member sees every applicant. Recommended for small single-team shops where per-user privacy is overhead.
Owner-only (per-team override)Even team owners only see their own work. The team behaves as a billing/membership grouping with no cross-member visibility — useful for teams of independent lawyers / accountants under a shared umbrella.

Strict is the default for agency-style orgs. Owner-only is per-team — set under each team's detail page.

How the three layers compose

There are three layers in priority order:

  1. Org default (the DataIsolationCard) — your baseline.
  2. Per-team override (a team's Visibility setting) — narrows for teams of independents.
  3. Personal opt-out (the MyKycPrivacyCard on the Teams page) — each individual user can choose to keep their own applicants private even if the org is in Open mode.

The page surfaces all three with a "Right now" banner that computes the effective rule. When a stricter upstream layer is in effect, the dependent card is dimmed with an explanation.

Teams tab

Team tree

The left column shows the team hierarchy as a tree. Top-level teams under the organization root; sub-teams nested below. Click any team to load its detail in the right pane.

Team detail

The right pane has:

  • Name + description — edit by clicking. Admins or team owners can rename.
  • Members section — every member of the team with their team role (team_owner / team_admin / team_user). Add, remove, change role. See Inviting teammates for the dialog details.
  • Team visibility — the per-team mode override (Team-shared / Owner-only).
  • Sub-teams — list of any children. Click to drill in.

Common workflows

Open Settings → Teams & Roles → Teams.
Click New team. Name it after the producer (e.g., "Alice Johnson").
The team is created empty. Open its detail.
Add the producer as team_owner.
Configure visibility per the team's needs.
Open the team's detail.
Click Add member.
Pick the Existing tab if they're already in the org; Invite if they're new (sends an email); Create if you want to admin-create the account.
Assign the team role: team_owner for the producer, team_user for the assistant.
Save. The new member can sign in (or sees the team appear if already in the org).
Open the source team's detail.
Remove the member.
Open the destination team.
Add them under the new team role.

Their applicants stay where they were — only the team mapping changes. To also reassign applicants, do that from the KYC list.

Roles & Permissions tab

This tab is hidden unless you have the team.custom_roles permission. Owners and admins always have it.

Every page and action in the workspace is controlled by a permission. When a member's role doesn't include it, the entry disappears from the navigation, the page shows "Ask your administrator for permission", and the API refuses the call. Owners and admins always have every permission.

Permissions decide what someone can do. Which records they see is still set by ownership and Teams: their own work, applicants they manage, records shared with their team, and everything under a team they lead. For an org-wide view (auditor, compliance officer), add them to the top-level team or switch the isolation mode to Open.

Built-in roles

RoleDefault permissions
OwnerEvery permission. Can't be changed.
AdminEvery permission. Can't be changed.
MemberView KYC/KYB, case comments, audit log, CSV export, live verifications (view, schedule, host), forms, AML alerts and monitoring, analytics, reports, usage.

Predefined roles

Every organization gets these ready-made roles, so you can onboard your team without building roles from scratch. They're marked System: you can't delete or rename them, but you can change their permissions or Clone one into a custom role.

RoleForKey permissions
Compliance officer (MLRO)Programme oversightManual and second review, manage requests, document export, audit log, AML, verification policies, KYC/B settings, reports
KYC reviewerAnalystsView, manage requests, manual review, comments, audit log, AML alert review
Senior reviewer (approver)Dual approvalReviewer permissions + second review, document export, recordings, monitoring
Live verification agentLive ID verification agentsView requests, schedule and host live ID verification sessions, comments
SupportApplicant help deskSend and resend requests, resubmissions, reminders, comments, schedule live ID verification sessions (no decisions)
SalesCustomer onboardingSend KYC/KYB requests, form links, schedule live ID verification sessions, analytics
Secretary / assistantAdmin supportSend requests and reminders, book live ID verification sessions
Report analystReportingRead-only analytics, usage, regulatory reports, CSV export
Auditor (read-only)Internal and external auditRead-only cases, audit log, alerts, reports, recordings
DeveloperIntegrationAPI keys, webhooks, Live ID Validation keys, all forms (incl. submissions), automation (workflows and risk policies), analytics, reports and usage; sees and creates verifications (masked data, no ID pictures) and the audit log to test the integration
Billing managerFinanceBilling details, invoices, credits, usage
Read-only viewerAnyone who only needs to lookView KYC/KYB, live verifications, analytics

Custom roles

Settings → Teams & Roles → Roles & Permissions → New role, or Clone an existing role.

Name it (for example "Compliance reviewer") and add a description.

Tick the permissions to include. They're grouped by area, and each group has a Select group shortcut.

Save. Assign the role from the Members tab.

Some permissions are as powerful as an admin, because they decide who can do what: Custom roles, Manage members, Identity & SSO, Security settings and KYC/B settings. Give them only to people you trust. Some guardrails apply: someone who isn't an admin can't change their own role, edit the role they hold, or grant the Owner or Admin role. KYC/B-settings editors can't change the manual-approval and export lists or the isolation mode.

Permission catalogue

GroupPermissionAllows
KYCkyc.requests.viewList and open verifications within the user's data scope
kyc.requests.createSend new KYC requests
kyc.requests.manageSend reminders, request resubmissions, re-run analysis, reassign
kyc.requests.deletePermanently delete requests
kyc.manual_reviewApprove or reject manually, including bulk decisions (custom roles; base roles follow the manual-approval list in KYC/B settings)
kyc.second_reviewSecond approval for dual-approval cases (custom roles)
kyc.case_commentsAdd and delete case notes
kyc.requests.exportExport the request list as CSV
kyc.documents.viewSee the pictures of identity documents and selfies — watermarked with the viewer, every view logged (owners and admins always; opt-in for other roles). Without it, the assigned reviewer sees them only while the case is in review, and a live ID host only until the request is decided
kyc.documents.exportDownload documents, evidence packs and results (custom roles; base roles follow the export list)
kyc.audit_logAudit log page
KYBkyb.requests.view / createThe same for business verifications
Live ID verificationlive_verification.viewLive ID verification list and session details
live_verification.scheduleSchedule, reschedule and cancel sessions, and send invitations
live_verification.hostRun sessions: start, pause, end, review documents, record decisions
live_verification.recordingsWatch and download recordings
Live ID Validationlive_id.manageIssue and revoke Live ID Validation keys
Formsforms.create / edit / deleteForm-builder actions
forms.public_linkPublic links and form tokens
forms.submissions.viewSubmissions and deliveries
Automationkyc.policiesVerification policies
automation.workflowsAutomation workflows
AMLaml.alerts.view / aml.alerts.reviewView and resolve alerts
aml.ongoing_monitoringEnroll, pause and cancel monitoring
Analyticsanalytics.dashboardAnalytics page
analytics.reportsRegulatory reports
billing.usage.viewUsage page
Developerapi.accessAPI keys and developer portal
api.webhooksWebhook endpoint, signing secret and deliveries
Teamteam.invitations / team.members.manage / team.custom_rolesInvite members, assign roles, manage roles
Settingssettings.verificationKYC/B settings
settings.live_verificationLive verification settings
settings.privacy_policyPrivacy policy
settings.securityTwo-factor and IP allowlist rules
settings.ssoIdentity & SSO, SCIM
branding.white_labelWhite-label settings
Billingbilling.customer_portalSubscription details, payment methods, billing details (plan changes and cancellation stay owner-only)
billing.invoicesInvoices
billing.creditsBuy credits

Troubleshooting

"Roles & Permissions" tab is missing

You don't have the team.custom_roles permission. Owners have it; ask your owner to either grant it to you or to create the role themselves.

A member can see applicants they shouldn't

Check the data-isolation mode. Open mode = everyone sees everything by design. Switch to Strict.

A member can't see applicants they should

Either the mode is too strict (set to per-team "Owner-only" override), or the applicants aren't assigned to them as primary/secondary manager. Reassign via the KYC list Manage managers menu.

Deleting a team — what happens to the applicants?

You're prompted with two modes:

  • Reassign (default) — applicants move to "no team" with a _previousTeamName flag. The team is soft-deleted; historical audit log entries still resolve.
  • Cascade delete — applicants AND all their data permanently deleted. There's a compliance warning. Use only when you're sure.