01
Pick a focused starting point
Choose one credential, approval, or operational process.
For organizations
Give your team a shared record to work from.
Issue digital records, check incoming information, and keep an evidence trail across the processes your organization runs.
For organizations
One organizational workspace for operators and developers
The business console brings issuers, verification, roles, and workflow records into one workspace. Start with a specific process, then connect the additional controls and integrations it needs.
Discuss support, deployment, data handling, and availability requirements before a larger rollout. Advanced capabilities depend on the agreed plan and configuration.
For organizations
Define the process, assign owners and validate the rollout
02
Set up the workspace
Configure identities, roles, data, and required integrations.
03
Review before expanding
Test the full user journey, evaluate the results, and add capabilities as needed.
Details and limitations
Team responsibilities and enterprise acceptance
A workspace for the whole delivery team
Business operators and developers work in the same Console. Operators manage organizational issuers, roles and review processes; developers configure the APIs and integrations that connect those records to existing systems. A recipient can still inspect a public proof through Verify without joining your workspace.
Start by naming the owner of the first use case, defining which information is private and assigning the minimum required access. Test with non-sensitive records in sandbox. Complete the applicable identity, country and production-access checks before using a production workflow or enabling paid billing.
Agree on an observable acceptance test
Follow one real workflow from creation through recipient verification, including rejection and recovery. Document who can issue, revoke or export records, which provider credentials are needed and which operations incur usage. A dashboard showing a configuration is not proof that every external action has completed.
Enterprise assurance requires operational evidence as well as software controls. Review the technical library, data-handling terms and available evidence with your team. Confirm deployment, retention, support and contractual requirements directly; do not infer a certification or service-level guarantee from a product page.
Two workspaces. Choose by what you want to do.
Building an app? Start in Console.
Developers, businesses and teams share the same Console. Verify is for personal records and checking shared proofs. You do not need a large team to choose the developer path.
console.truthlocks.com
Business & Developer Console
Build with APIs and SDKs, manage workspace credentials, register issuers and AI agents, invite teammates and review usage. Start in sandbox, then complete onboarding for production.
Create a Console workspaceverify.truthlocks.com
Personal Verify portal
Manage your own documents, credentials and signed statements. Share a proof link with someone who needs to check your record. Personal plans and records stay in this portal.
Create a personal accountOnly checking a record? Open public verification. No account is needed for an intentionally public proof. Compare accounts and sign-in options.
Before you start
The details that matter.
I'm a developer working alone. Which account do I need?
Use Business & Developer Console when you are building an application, integrating an SDK, managing agent identities or configuring workspace API access. Choose it even when you are the only person building the integration. Enter accurate project and organization information; production access still requires the applicable onboarding checks.
Is there a separate developer console?
No. Developers and organizations use Console at console.truthlocks.com. Documentation explains how to build; Console is where you manage the workspace, credentials, issuers and environments used by your integration.
What is Verify for?
Verify at verify.truthlocks.com is the personal portal for your own records and statements, and the public place to check shared proofs. A personal account is not the workspace for your company's team, organizational issuers or business integrations.
Do recipients need an account to check a public proof?
No. Open an intentionally public proof link or the public verification page. Creating and managing records requires the appropriate account; inspecting public evidence does not. Private records remain subject to access controls.
I already signed up in Verify. How do I build an integration?
Keep your personal records in Verify. Create or join the appropriate Console workspace for the integration, and use its credentials with the matching API environment. Signing in to Verify does not automatically move personal records, subscriptions or permissions into Console. Contact support if you need help choosing or locating a workspace.
Does choosing Console enable production or paid usage immediately?
New business workspaces begin in sandbox. Complete the required onboarding and approval steps before production access. Billing country verification, account permissions, plan limits and provider setup still apply. A sandbox example is not evidence of production readiness.