Skip to main content
Enigm Command is the web control panel product in the Enigm ecosystem. It is the administrative and account-management surface for individual users, organizations, and enterprise administrators. Enigm Command is not a messaging client. It must not provide access to message plaintext, secure call content, private key material, decrypted attachments, or implementation-sensitive communication state.

​
Overview

Enigm Command provides authorized workflows for account creation, account lifecycle, connected-device visibility, active session control, critical-operation PIN authorization, product lifecycle management, payment workflows, Enigm Link lifecycle governance, Enigm Server administration, Enigm eSIM management, Enigm Key lifecycle visibility, Enyra Product Assistant, training, Active Defense review context, and managed-device operations. Enigm Command supports administrative visibility into security state, but security state visibility is not equivalent to message visibility. The diagram is conceptual. It shows administrative surfaces, not internal routes or operational topology.

​
Core Responsibilities

Enigm Command is responsible for:
  • Account lifecycle and deletion workflows.
  • Account creation workflows.
  • Platform data deletion workflows where policy and legal boundaries allow.
  • Critical-operation PIN authorization for high-impact actions.
  • Active session review and closure.
  • Connected-device visibility and device removal.
  • Device revocation and replacement workflows.
  • Enigm OS managed-device lifecycle when the user enables managed-device mode.
  • Supported product purchase, entitlement, and lifecycle workflows.
  • Enigm Link purchase, official USB registration, update eligibility, device lifecycle state, and support workflows.
  • Enigm Server purchase, creation, region selection, join request review, membership, content lifecycle, and deletion.
  • Enigm eSIM purchase, activation lifecycle, account association, unlinking, deletion, and retirement.
  • Enigm Key associated-device visibility, loss handling, revocation, and replacement.
  • Enyra Product Assistant guidance for account, device, product, configuration, and navigation workflows.
  • Essential or advanced Enigm training with final-exam workflows.
Product lifecycle visibility is not protected content visibility. Enigm Command product workflows must remain separate from message plaintext, secure call content, media content, attachment plaintext, user conversations, and private key material.

​
Account Creation And Critical PIN

Enigm account creation is performed through Enigm Command. The onboarding workflow establishes username and password credentials, recovery phrase handling, 6-digit numeric PIN setup, account identity creation, and initial trusted-device association. PIN validation is performed against the Enigm server-side security layer. Critical Enigm Command operations, including platform data deletion and account deletion, require PIN authorization according to policy. The PIN authorization model must not be described as a local-only device check. It is an account security control that supports high-impact lifecycle decisions while remaining separate from message plaintext and private key material.

​
Training

Enigm Command includes a training area for Enigm product education. Training can include:
  • Essential Enigm usage training.
  • Advanced Enigm usage training.
  • Product security guidance.
  • Final-exam workflows.
Training records are product education and account lifecycle records. They do not provide access to protected communications or private key material.

​
Documentation Map

  • Product Lifecycle explains product purchase, activation, entitlement, and lifecycle workflows.
  • Device and Session Management explains account, device, session, managed-device, and remote-wipe boundaries.
  • Enyra Product Assistant explains product guidance and the boundary between product assistance and security intelligence.
  • Payment Privacy explains payment methods, reduced identity linkage, Code Coin, invoices, and commercial boundaries.
  • Enigm Link explains the secure USB environment governed through Enigm Command.

​
Security Boundaries

Enigm Command has explicit security boundaries:
  • Enigm Command does not provide access to message plaintext.
  • Administrative capabilities do not bypass end-to-end encryption.
  • Device management and message access are separate trust domains.
  • Enigm Server management and message plaintext access are separate trust domains.
  • Enigm Link lifecycle governance does not provide access to protected communications, private key material, or local browser session content.
  • Server-scoped lifecycle controls affect encrypted content availability and lifecycle, not content visibility or decryption.
  • Security state visibility is not equivalent to message visibility.
  • Enigm Command actions must not expose private key material.
  • Product assistance must not expand access beyond the user’s authorized Enigm Command role.
Administrative workflows should be authenticated, authorized, scoped, and auditable.

​
Privacy Considerations

Enigm Command should expose only the information required for administrative review, device lifecycle control, policy management, product lifecycle, and security event visibility. Privacy considerations include:
  • Use Privacy-Preserving Device Handles for device correlation.
  • Avoid exposing unnecessary identity metadata.
  • Separate account state from message content.
  • Separate device lifecycle state from message plaintext.
  • Separate product lifecycle state from protected communications.
  • Minimize security event metadata to what is required for review and audit.
  • Limit Active Defense network-behavior finding visibility to authorized review contexts.
  • Avoid exposing protected content in administrative views.
See Platform Limitations.

​
Threat Model References

Relevant threat-model areas include Enigm Command abuse, account and app compromise, device lifecycle abuse, Enigm OS policy bypass where deployed, managed device misuse, product lifecycle abuse, and loss of audit visibility.