Keymint IconKeymint IconKEYMINTdocs
DocumentationAPI Reference
BlogDashboard
Keymint IconKeymint IconKEYMINT
SectionsDocumentationAPI Reference

Getting Started

  • Keymint Documentation
  • Introduction
  • Getting Started
  • License Keys
  • Changelog

SDK References

  • Software Development Kits (SDKs)
  • Node.js SDK
  • Go SDK
  • Python SDK
  • C# SDK

Integration Guides

  • Integration Guides
  • Customer Portal for Vendors
  • Team Roles & Permissions
  • Radar Alert Destinations
  • Payment Provider Integrations
  • Stripe Subscription Licensing
  • Email Delivery
  • API Key Management
  • Webhook Deliveries
  • Analytics and Retention
  • Dashboard Workflows
  • Electron Licensing
  • PyQt Licensing
  • Tauri Licensing
  • Next.js SaaS Licensing

Licensing Guides

  • Licensing Concepts
  • Node-Locking & Machine Identifiers
  • Floating Licenses
  • Offline Verification
  • License Radar
  • Public Key Management and Rotation
  • Feature Flags
  • Webhooks & Events

Templates

  • Starter Templates
  • Electron License Starter
  • PyQt License Starter
  • Tauri License Starter
  • Next.js SaaS License Starter

Security & Trust

  • Security & Trust

Support

  • Frequently Asked Questions
  • Customer Portal
  • Using the Customer Portal
  • Team Settings and Roles

Legal

  • Privacy Policy
  • Subprocessors
  • Data Processing Agreement
  • Security Overview
  • Terms of Service
  • Service Level Agreement (SLA)
  • GDPR Compliance
Go to Dashboard

Getting Started

  • Keymint Documentation
  • Introduction
  • Getting Started
  • License Keys
  • Changelog

SDK References

  • Software Development Kits (SDKs)
  • Node.js SDK
  • Go SDK
  • Python SDK
  • C# SDK

Integration Guides

  • Integration Guides
  • Customer Portal for Vendors
  • Team Roles & Permissions
  • Radar Alert Destinations
  • Payment Provider Integrations
  • Stripe Subscription Licensing
  • Email Delivery
  • API Key Management
  • Webhook Deliveries
  • Analytics and Retention
  • Dashboard Workflows
  • Electron Licensing
  • PyQt Licensing
  • Tauri Licensing
  • Next.js SaaS Licensing

Licensing Guides

  • Licensing Concepts
  • Node-Locking & Machine Identifiers
  • Floating Licenses
  • Offline Verification
  • License Radar
  • Public Key Management and Rotation
  • Feature Flags
  • Webhooks & Events

Templates

  • Starter Templates
  • Electron License Starter
  • PyQt License Starter
  • Tauri License Starter
  • Next.js SaaS License Starter

Security & Trust

  • Security & Trust

Support

  • Frequently Asked Questions
  • Customer Portal
  • Using the Customer Portal
  • Team Settings and Roles

Legal

  • Privacy Policy
  • Subprocessors
  • Data Processing Agreement
  • Security Overview
  • Terms of Service
  • Service Level Agreement (SLA)
  • GDPR Compliance

Dashboard Workflows

Follow Keymint dashboard workflows for products, versions, templates, customers, imports, license generation, key lifecycle actions, and workspace permissions.

The dashboard is organized around a simple flow: create a product, optionally add versions and features, create customers, then generate and manage license keys.

Products and versions

Create products under Products. Product-level features become defaults for newly generated keys. Versions are optional release labels such as 1.0.0 or enterprise-2026; assign one during key generation when you need release-specific entitlements. Archive versions that should no longer be issued.

Saved templates

On a product’s Saved Templates tab, save reusable key-generation settings such as license type, activation limits, expiration, and feature flags. Templates speed up generation; they do not change keys that were already issued. Review the selected template before generating a batch.

Customers

Customers may be created individually or imported from Customers. CSV imports require name; email is optional. Fields containing commas must be quoted. Valid rows are previewed before creation, while malformed rows and duplicates are reported for review.

License lifecycle

Generate keys from a product, assign a customer or version when applicable, and use the license list to activate, disable, block, unblock, reset activations, export, or delete keys. A disabled or expired key will fail activation; a device-specific deactivation does not disable the entire key.

Permissions

Workspace roles determine which members can manage products, customers, keys, billing, and team settings. Keep administrative actions with owners/admins and use read-only access for reporting collaborators.

On this page

  • Products and versions
  • Saved templates
  • Customers
  • License lifecycle
  • Permissions