Skip to main content
When you first sign in to console.truthlocks.com, a guided wizard walks you through everything you need to start issuing attestations. The wizard detects your progress automatically — if you leave and come back, it picks up where you left off.

​
Prerequisites

  • A Truthlocks account. Sign up if you do not have one yet.

​
Onboarding steps

1

Tenant profile

Enter your organization’s basic information:
  • Name — your organization’s display name.
  • Slug — a URL-friendly identifier used in API paths and your console URL.
  • Contact email — the primary email for platform communications.
  • Country — where your organization is based (used for data residency).
This information is saved to your tenant record and can be updated later from Settings > Organization.
2

Organization

Create or select an organization within your tenant. Organizations let you group issuers, users, and attestations under a single entity. Enter:
  • Organization name — the legal or operating name of the organization.
If your tenant already has an organization, this step is skipped automatically.
3

Team invites

Invite team members by email and assign them a role:
RolePermissions
AdminFull access to all tenant resources, settings, and team management
MemberCreate and manage issuers, mint attestations, view audit logs
ViewerRead-only access to issuers, attestations, and audit logs
You can skip this step and invite team members later from the Team settings page.
4

Issuer profile

Create your first issuer — the entity that signs attestations on behalf of your organization:
  • Legal name — the issuer’s registered legal name.
  • Display name — the name shown on attestations and proof pages.
  • Website — the issuer’s public website URL.
  • Contact email — used for trust registry verification.
The issuer is created at assurance level L1 (basic). You can request a higher assurance level after onboarding by submitting compliance documentation.If your tenant already has an issuer configured, this step is skipped.
5

Signing keys

Generate an Ed25519 signing key for your issuer. This key is used to cryptographically sign every attestation your issuer creates.Click Generate keys and the wizard creates a key pair automatically. The public key is registered with the Truthlocks platform, while the private key is stored securely in the signing service.
Signing keys cannot be deleted once generated. If a key is compromised, use the key compromise endpoint to mark it as compromised and rotate to a new key.
If your issuer already has signing keys, this step shows the existing key details and lets you proceed.
6

Test mint

Verify your setup by minting a test attestation. The wizard provides a searchable list of attestation schemas organized into categories:
  • Identity — email verification, KYC, government ID
  • Employment — employment verification, background check, income
  • Education — degree, transcript, enrollment
  • Healthcare — license, immunization, insurance
  • Compliance — SOC2, ISO 27001, GDPR
  • Financial — accreditation, bank verification, credit
  • Skills — certification, assessment, portfolio
  • Supply chain — origin, quality, shipment
  • Other — custom claims
Select a schema, enter a recipient email address, and click Mint test attestation. The wizard calls the attestation mint endpoint and shows you the resulting attestation ID on success.
The test attestation is a real attestation recorded on the transparency log. You can verify it immediately using the verify endpoint.
7

Go live

The final step shows a checklist of prerequisites:
  • Tenant profile completed
  • Organization created
  • Issuer profile configured
  • Pipeline verified (test attestation minted)
When all items are checked, click Activate & go to console to complete onboarding and access the full console dashboard.

​
After onboarding

Once the wizard is complete, you land on the console dashboard where you can:
  • Mint attestations at scale via the console UI or API.
  • Configure webhooks to receive real-time event notifications.
  • Set up governance policies for multi-party approval workflows.
  • Manage API keys for programmatic access.

Quick start

Issue your first attestation via the API in under 5 minutes.

Core concepts

Understand tenants, issuers, attestations, and verification.

Environments

Sandbox vs. production environment configuration.

RBAC

Role-based access control and permission management.