SecurePoint USA

Trade

SECUREPOINT TRADE

Help

Admin sessionDEMO

Demo workspaceData, downloads, and workflow events are simulated for evaluation.

Product help

Trade Help & SOPs

Plain-language guides for every workspace — start with the new-user path if export compliance is new to you.

New user path

Learn Trade even if compliance is new

Follow these five steps in order. Golden paths below are for demos and buyer verification — start here for day-to-day learning.

Start with basics Guided practice

Step 1
New to export control?
Plain vocabulary — transaction, screening hit, license, evidence.
Export compliance basics →
Step 2
Pick your role path
Analyst, manager, admin, EO, or viewer — first-week checklist.
Start here by role →
Step 3
First week in Trade
Day-by-day orientation from Help to Import → Transactions → Approvals.
Getting started with Trade →
Step 4
Guided browser practice
Eight click-by-click steps in demo mode — verify Help matches the UI.
Guided browser practice →
Step 5
Learn a workspace
Open any module below, or press ? on the page for the Guide panel.
Transactions workspace →

Launch readiness

What is ready, what is beta, what still needs proof

Trade is ready for core compliance workflow demos. Some advanced modules are beta or pilot-scoped. SFTP intake is built behind a flag but is not production-ready until transport proof and a production secret resolver are complete.

Open full article

Module status

Trade Core
LIVE
Workspace shell, audit, dashboard, navigation.
Transactions
LIVE
Screening, intake, holds, certification.
Approvals
LIVE
Adjudication with audit-row rationale.
Evidence
LIVE
Regenerable packs from stored workflow data.
Import / CSV Intake
LIVE
Manual + CSV ingest with validation surfacing.
Analytics
LIVE
Queue pressure, license risk, diversion signal views.
Settings / API Keys / Connectors UI
LIVE
UI live; connector maturity varies — see caveats.
Licensing
BETA
Headers, lines, drawdowns, alerts, documents, transaction linkage.
License Applications
BETA
Draft → EO approval → JSON packet → manual submission log.
CDD secure_portal
OPERATOR-READY
Pilot-scoped, behind NEXT_PUBLIC_CDD_ENABLED.
CDD outbound transports
NOT SHIPPED
SharePoint / Cryptshare / SFTP / FAA SharePoint — proof-contract stubs only; fail closed.
Inbound SFTP
PARTIAL
Adapter behind SFTP_ADAPTER_ENABLED; not production-ready.
SFTP production secret resolver
NOT SHIPPED
In-memory resolver in tests; Vault/KMS deferred.
SFTP real customer transport proof
UNVERIFIED
Tier-3 staging transport checklist pending.

What we will not claim

No production-ready SFTP transport.
No live ERP integration; no direct SAP, Oracle, or NetSuite sync.
No direct regulator filing; no automated BIS or DDTC submission.
No outbound CDD SFTP support; outbound SFTP for CDD is a stub.
No PDF license application packets — Trade emits JSON only.

Core demo

Open Dashboard — confirm queue pressure tiles render.
Import or view Transactions — confirm rows and screening signals.
Review a held item in Approvals — claim, inspect, record a disposition.
Generate an Evidence pack — confirm regeneration completes.
View the Audit trail — confirm append-only rows scoped to org.
Open a Help article — confirm new-user path and contextual hints.
Confirm module statuses on this page match the demo script.

Pilot

Licensing demo path — present as BETA.
License application EO path — present as BETA; JSON packet only, no PDF, no direct filing.
CDD secure_portal path — present as OPERATOR-READY pilot behind feature flag.
SFTP stays off unless explicitly staged — never flip SFTP_ADAPTER_ENABLED in production.

Proof

Platform handoff smoke — pending real-handoff staging walkthrough.
SFTP Tier-3 transport proof — pending per staging validation runbook.
Production secret resolver (Vault / KMS) — pending; tests still use the in-memory resolver.
Full customer staging walkthrough — pending separate staging alias and end-to-end run.

Demo command center

A clean talk track for every buyer demo

Four demo paths with the click sequence, the line to say, the line to avoid, and the proof point that matters. Use it before sales conversations so the room stays honest about LIVE, BETA, OPERATOR-READY, and PARTIAL modules.

Open full article Open prep checklist Operator golden paths

Demo rules

Start with core LIVE paths first — clean transaction, denied-party match, evidence — before touching beta or pilot modules.
Mention beta and pilot labels plainly. Buyers respect honesty more than polish.
Keep SFTP off unless explicitly staged. The product is fail-closed there for a reason.
Use Help articles as proof, not promises — open the article in a tab while you demo.
If asked about ERP integrations, say CSV and manual intake are live and deeper connector work is scoped per deployment.

Demo path 1

LIVE

Clean transaction

Show the normal intake, screening, and certification workflow.

Click path

Open Dashboard — call out queue pressure tiles.
Open Transactions — show the operator queue.
Select a clean row with complete classification and no holds.
Review the disposition; point to the screening reference and audit row.
If an evidence pack exists, jump to Evidence and show regeneration.

Trade helps the team see transaction risk quickly, move clean work forward, and keep a defensible record.

What this proves

Every disposition produces a screening reference, an audit row, and a regenerable evidence pack on demand.

Do not say

Automated ERP sync is live.
Trade replaces your ERP.
Every transaction auto-clears.

Recovery: If the row you picked has any banner (policy review, partial screening, drawdown alert), swap to a different row rather than improvising — do not try to explain banners on a "clean" demo.

Open full guide Go to /transactions

Demo path 2

LIVE

Possible denied-party match

Show a held transaction and the human adjudication workflow.

Click path

Open Dashboard — note holds on the queue strip.
Open Approvals — show the review queue.
Open a held item — inspect the screening flags and party detail.
Walk through claim → decision → rationale on the record.
Point to the audit row that captures actor, decision, and rationale (no raw PII in metadata).

When something needs human review, Trade makes the queue, the rationale, and the audit trail visible to the right people.

What this proves

Holds are visible, adjudications are role-gated, and every decision writes an append-only audit row scoped to the organization.

Do not say

Trade auto-denies every hit.
Trade replaces legal judgment.
Adverse media controls disposition automatically.

Recovery: If no held row is available in the demo dataset, walk the Approvals empty state and use the Help link there — do not invent a hit.

Open full guide Go to /approvals

Demo path 3

BETA

License required

Show license awareness, drawdown context, and beta posture.

Click path

Open Licenses — show the active license list and BETA badge.
Open one license — point to conditions, remaining balance, and linked documents.
Switch to Transactions or the license detail to show a linked or license-required transaction.
Explain how the operator links a transaction to a license before release.
Optionally point to /help/license-applications for the EO packet workflow (also BETA).

Licensing is beta, but already shows the workflow direction: connect license records, conditions, drawdowns, and transaction context — without overpromising regulator automation.

What this proves

Operators see remaining capacity and conditions per license, link transactions explicitly, and never silently overdraw.

Do not say

Licensing is final GA.
Automated regulator sync is live.
Trade files BIS or DDTC applications for you.

Recovery: If a buyer asks for portal sync, anchor on "JSON packet today, EO uploads at DECCS or SNAP-R" — do not promise dates for direct filing.

Open full guide Go to /licenses

Demo path 4

LIVE

Evidence request

Show the strongest value: proof on demand for a chosen transaction.

Click path

Open Evidence — show the workspace header and any recent packs.
Select a transaction with stored workflow data.
Generate or regenerate the evidence pack.
Walk the pack contents — screening, decisions, manifest, audit ties.
Cross-link to Audit to show the underlying append-only rows.

This is the big one. Trade is built to answer three questions: what did we screen, what did we decide, and what proof do we have? Evidence packs make that answerable in seconds.

What this proves

Evidence packs assemble from live workflow data — they reflect what was actually stored, including any intentional fail-closed gaps.

Do not say

Evidence can invent missing screening results.
PDF license application packets are shipped (Trade emits JSON).
CDD outbound SFTP delivery is live.

Recovery: If a transaction has intake gaps and the pack shows them, frame it as intentional fail-closed transparency, not a defect — that is the point.

Open full guide Go to /evidence

Every quoted talk-track line is a starting point — adapt to the room. Never improvise status labels, regulator-filing claims, or SFTP readiness on the fly.

Demo data readiness

What sample records you need before the call

One sample per demo path. Each card tells you what data must exist, how to know it is ready, what to do if it is missing, and what you must never improvise.

Demo data readiness is not product state. It is a pre-call checklist. If the record is missing, do not improvise the claim — fall back to Help articles and walk the workflow.

Sample 1

LIVE

Clean transaction sample

Demo path: Clean transaction

Required data

One transaction with complete classification.
Complete party data on both sides of the row.
No active holds on the transaction.
Screening complete with a stored result reference.
Clean disposition or a certifiable state.
Audit trail rows available for the row.

Ready signal

You can open Transactions, select the row, and explain why it is clear without invoking any banner.

If the data is missing

Walk the Transactions list and open the Help article. Do not pretend a held or incomplete row is clean.

Do not fake

No silent auto-clear claims.
No pretending missing classification is acceptable.
No claiming every row clears automatically.

Open guide Go to /transactions

Sample 2

LIVE

Held / possible denied-party sample

Demo path: Possible denied-party match

Required data

One transaction in review or hold state.
Screening flag or policy reason visible on the record.
Approval and adjudication path available for your role.
Audit trail rows tied to the hold and decision.

Ready signal

You can open Approvals and explain why human review is required for the chosen item.

If the data is missing

Walk the empty state and the Approvals workflow article. Do not invent a hit.

Do not fake

No fake denied-party match.
No auto-denial claim.
No legal judgment replacement claim.

Open guide Go to /approvals

Sample 3

BETA

License-required sample

Demo path: License required

Required data

One active license on the org.
License conditions or remaining balance visible.
One linked or license-required transaction.
Drawdown or remaining-capacity context visible on the record.

Ready signal

You can open Licenses and show why licensing matters to a specific transaction.

If the data is missing

Frame Licensing as BETA and open the Licenses help article. Do not claim GA.

Do not fake

No direct BIS or DDTC filing claim.
No automated regulator sync claim.
No final GA language.

Open guide Go to /licenses

Sample 4

LIVE

Evidence-ready sample

Demo path: Evidence request

Required data

One transaction with stored workflow data.
Screening result exists for that transaction.
Decision or disposition recorded.
Evidence pack can generate, or an existing pack can be reviewed.
Audit trail rows tied to the transaction.

Ready signal

You can open Evidence and show proof assembled from stored workflow data.

If the data is missing

If the pack shows gaps, frame intentional fail-closed transparency as the point — do not invent missing pieces.

Do not fake

No invented evidence.
No claim that packs backfill missing screening.
No CDD outbound SFTP claim.

Open guide Go to /evidence

New here?

Export compliance basics

Plain-language Trade vocabulary for people new to export control — what transactions, screening hits, licenses, and evidence mean in the product.

Getting started

Getting started with TradeLive

What Trade is, how you arrive from SecurePoint, and the core workspaces every compliance operator uses.

Export compliance basicsLive

Plain-language Trade vocabulary for people new to export control — what transactions, screening hits, licenses, and evidence mean in the product.

Start here by roleLive

First-week paths for analysts, managers, admins, and Empowered Officials — which workspaces to open and which to avoid.

Guided browser practiceLive

Click-by-click checklist for a new compliance analyst in demo mode — follow Help in the browser and confirm each screen matches expectations.

Trade Launch ReadinessLive — position carefully

Per-module readiness state — what is live, what is beta, what is pilot, and what still needs proof.

Trade Demo Command CenterLive — position carefully

Sales-facing talk track for four core demo paths — what to click, what to say, what not to say, and what each path proves.

Trade Demo Prep ChecklistLive — position carefully

A one-page printable pre-call checklist. Use it ten minutes before a Trade demo; walk top to bottom, then print or hand off.

Modules

Transactions workspaceLive

Create, review, and certify export transactions; understand disposition flags and missing-data blocks.

Golden path 1

Approvals and adjudicationLive

Work the adjudication queue, assign reviewers, and record decisions with audit-backed rationale.

Golden path 2

Transaction evidence packsLive

Regenerate evidence packs from real transaction, screening, and decision data for audits and customer requests.

Golden path 6

Active export licensesLive — position carefully

Track active licenses, remaining value and quantity, drawdowns, alerts, and expiry.

Golden path 3

License applicationsLive

Draft applications, route Empowered Official approval, generate JSON packets, and log manual regulator submission.

Golden path 5

Import and intakeLive

Bring transaction data in via CSV upload or manual intake; monitor processing jobs.

Analytics and queue healthLive

Read risk concentration, disposition trends, escalation pressure, and diversion signals — triage input for Approvals, not a substitute for row-level decisions.

Controlled Data DeliveryRestricted mode

Request, approve, package, and prove controlled outbound transfers. secure_portal is the shipped delivery path.

Golden path 7

Settings and administrationLive

Configure connectors, API keys, escalation behavior, and org-level controls — admin and manager surfaces.

Compliance policiesLive

Organization-specific release rules, diversion catalog, and embargo references that feed the decision engine.

Workflows

Eight buyer verification scenariosLive

The canonical golden paths every compliance buyer expects — use these to demo, train, and audit Trade end to end.

Roles

Roles and permissionsLive

What admin, manager, analyst, viewer, and itar_enclave roles can do across Trade workspaces.

Troubleshooting

Troubleshooting quick referenceLive

Symptom → likely cause → action for the most common Trade workspace failures.

Getting human supportLive

When to use in-product help, when to contact your administrator, and standard support expectations after onboarding.

Capabilities not available yetNot shipped

Explicit boundary list so you do not expect regulator filing, ERP adapters, or external CDD transports.

Demos & buyer verification

Eight canonical scenarios compliance buyers use to score Trade. Use after the new-user path above — not as your first day in the product.

Golden path 1

Clean transaction

Screened, complete data, no holds — certify and produce evidence.

Golden path 2

Possible denied party match

Screening hit enters adjudication; record a decision with audit rationale.

Golden path 3

License required

Transaction needs an active license; link and draw down correctly.

Golden path 4

Overdraw attempt

Export would exceed license capacity — system must block the drawdown.

Golden path 5

License application workflow

Draft → EO approval → JSON packet → manual portal submission → active license.

Golden path 6

Evidence request

Regenerate a transaction evidence pack and verify contents.

Golden path 7

Controlled Data Delivery

secure_portal delivery with packaging, approval, and access proof.

Golden path 8

Incomplete transaction

Missing classification, party data, or screening — gaps surfaced, certification refused.

Read the full golden paths guide

Need human support?

Search Help first. If you still need SecurePoint, include workspace and UUID context only — never party names, screening payloads, or secrets.

Workspace: /help
Organization ID: 00000000-0000-0000-0000-00000000a711

Email support@securepointusa.com