Skip to main content
6Sandbox
Demo note

Settings here are fully editable and session-persisted, just like production — nothing is written to a real backend, and MFA setup is simplified (no real QR code or authenticator device required).

Configuration & tools

Settings

Workspace profile, review policy, and notifications

Organization profile

New submission and drift alert notifications arrive here.

Review policy

Stripe verification
Applicants verify company, bank account, and signer identity directly with Stripe. Recommended for production.
Auto-verification — handled by Stripe
Disabled while Stripe verification is on.
Hide score from applicants
Applicants see verification progress, never the number — your reviewers always see it

Fraud network

Ring detection matches hashed applicant attributes (officers, addresses, bank fingerprints) across every DAF Connect workspace to catch fraud rings no single workspace could see.

Share organization names with the network
When a ring match involves one of your applicants, reviewers in the other workspace see that organization's name in the evidence — and you see theirs. Turn this off to keep your applicants' names anonymized to other workspaces (matches still occur on hashes). Which workspace an organization applied to is never revealed either way, and bank accounts always stay last-4 masked. See it on the Entity graph page: RING-001's cross-workspace org shares its name, RING-003's arrives anonymized.

Two-factor authentication

Your MFA method
How you verify your identity on sign-in
Email verification

Switch to a different method:

Demo note

In production, switching methods walks you through a real emailed code or a QR code to scan with your authenticator app. The demo applies the switch immediately.

Team MFA policy
Control which MFA method team members must use
Default for all members
Per-member overrides
Sarah Chen
sarah.chen@acmecorp.com
Marcus Williams
marcus.w@acmecorp.com
Priya Patel
priya.p@acmecorp.com

Per-member overrides take priority. When locked, the user cannot change their own method.

Email notifications

New submission received
When a non-profit submits an application
Decision required
When a submission has been in review over 5 business days
Drift alert raised
When data inconsistencies are found on an approved partner
Watchlist alert
When IRS or OFAC status changes on an approved partner

API & webhooks

Endpoints, events & signing secret
Delivery log and per-submission authorization live with the endpoint
Embed key & allowed domains

Data retention

What this means: Rejected and withdrawn submissions older than this period will be archived for 30 days, then permanently deleted.

IRS guidance recommends 7 years for charitable contribution records.

Dark web & surface web screening

Powered by Klaw

Screens every contact on a submission in one batch — the applicant plus each officer on file — against breach corpora, sanctions and denylists, and surface-web exposure. The application is scored worst-case: the most exposed contact sets the number, never the group's average, and a contact that could not be screened comes back as an error, never a pass.

Klaw screening: sandbox
Derived from the workspace's own mode — there is no separate Klaw switch. A workspace in sandbox sandboxes everything at once: Stripe, Klaw, the lot. Sandbox runs the real pipeline against fixture addresses and is never billed — results come back shaped exactly like live ones, so they are labelled as fixtures everywhere they appear. Live screens the applicant's real contacts and is metered.
SANDBOX
In sandbox because this workspace is in sandbox mode. A workspace being demonstrated must never spend a metered call screening a real person's real details. Turning the workspace out of sandbox mode takes Klaw live with it — there is nothing separate to flip.
Demo note

This demo workspace is in sandbox mode, so Klaw screening is in sandbox with it — one workspace switch covers Stripe, Klaw and everything else, and there is no separate Klaw control anywhere in the product. Every dark web finding in this demo is a stored fixture carrying sandbox markers for exactly this reason. Take a workspace out of sandbox and all of it goes live together.