Docs · Getting started & concepts
Console
Sign-in
Console supports Microsoft work or school accounts, Google, and Apple. When your operator has
enabled it, you may also use Sign in with email code for a Liminal Keys
account (one-time passcode sent to your email). Choose Sign in with Microsoft,
Continue with Google, or Continue with Apple. Social and
Microsoft work paths open a brief Microsoft-hosted Liminal Keys page (address may show
ciamlogin.com). If Microsoft federation is blocked by IT and email code is
enabled for your environment, use the same address your invitation was sent to and enter the
code from your email when prompted.
After sign-in, Console checks your workspace once. If that fails, the screen offers Retry workspace check and Sign out and try again. Prefer Microsoft work or school if Google authorization keeps timing out; clear site data for console.liminalkeys.com only if sign-out alone does not help. Operators: pending API database migrations can also block workspace load — see product ops docs.
Each provider is a separate Console identity until you link them explicitly. See Linked sign-in methods when the same person uses Microsoft, Google, or Apple with one email address.
Signing identities
Onboard signing identities whose private keys stay non-exportable in Key Vault:
- Import — upload a password-protected PKCS#12 once; the private key is imported once into non-exportable Key Vault custody
- Generate — create a key in custody, download a CSR, issue the certificate with Apple, then complete the identity
- Self-signed (testing) — mint a short-lived self-signed leaf (up to one year) for agents and automation experiments. Console labels these identities as testing only — they are not trusted by PDF readers or mail clients.
Pending, failed, or expired identities never appear on enrolled Macs and cannot be used in policy.
Self-signed testing identities are active immediately; allow them in policy before agents call
sign_hash or fetch get_certificate_chain.
AI agents
Register workspace agents (for example Claude Code connectors), set optional signing caps, and issue short-lived API keys. Keys are shown once at issue time — store them in your agent secret store immediately. Signing stays deny by default until a policy rule includes the agent as a subject. Suspend an agent to block new signs without revoking its enrollment device record. MCP setup: AI agents & MCP guide and Console → AI agents (connector URL + API keys). Use Require approval on agent rules when you want a human gate; approvers use the LK Approvals web app (optional web push). Liminal Keys is not a qualified trust service provider.
Policy rules
Rules are the operational control plane for signing. Each rule specifies:
- Identity — which virtual certificate may be used
- Subjects — directory user, directory group, enrolled Mac, registered AI agent, or CI workload (trusted issuer / enrollment key). Rows of the same type are alternatives; different types must all match. CI workload subjects cannot require user confirmation; AI agents use Require approval for human gates.
- Operation — sign (v1)
- Confirmation — optional; not yet supported by the macOS agent (matching signs are denied — leave unchecked for now)
- Validity window — optional start/end times
- Enabled — disabled rules do not grant signs even after apply
Edits are drafts until you click Apply policy. Until applied, a change MUST NOT grant signing. No matching applied rule means deny. If one applied rule would allow and another would deny the same request, the result is deny.
CI & automation
Configure GitHub OIDC trust (repository, runner type, optional branch/workflow/environment restrictions), CI enrollment keys, identity SHA-1 thumbprints for workflows, and recent CI enrollments. The tenant ID is also shown at the top of this page with Copy. Workflow YAML is maintained in the public sample repo Quickstart. See CI & pipelines.
Devices & enrollment
List enrolled Macs, revoke a machine that leaves the fleet, and issue short-lived enrollment codes for Liminal Keys for Mac. Treat codes as secrets — do not post them to shared mailing lists. Revocation stops signs from that device on the next request.
Sign audit
Review allow and deny outcomes with resolved device, identity, and rule names where available, plus timing. Each record includes DigestHashHex — the 64-character uppercase SHA-256 hash of the signed digest. The table shows the first 16 hex characters followed by …; use Copy for the full hash. Agent-initiated signs also show the agent-supplied document label. Raw 32-byte digest bytes, CMS signatures, and private key material are not stored or downloadable.
Users & groups
Invite people by email when they should sign in with Google, Apple, or another supported login. Create an invite link in Console, copy it, and share it yourself — Liminal Keys does not send invitation email. The invitee signs in, accepts the link, and is bound as a non-admin user. You can issue an enrollment code for a pending invitee so they enroll a Mac without opening Console. You can also add or update users and groups by identifier, and assign group membership, for policy subjects. Invites never grant tenant-admin access.
Billing & usage
Tenant administrators see used vs soft cap for signing identities and enrolled Mac signer nodes on the Billing page and on Signing identities and Devices when you are close to or at a cap. Counts come from the API (active and pending identities count toward the identity cap; enrolled Macs count toward the signer-node cap). Proximity hints such as “one slot remaining” help you plan add-ons or contact support@liminalkeys.com before you hit a limit.
Workspace settings
Tenant administrators rename the workspace display name from Workspace settings
(Admin in the sidebar; hash #account).
The workspace tenant ID (lowercase UUID) appears on that page with Copy —
use it as LIMINAL_KEYS_TENANT_ID / GitHub Actions tenant-id and in the OIDC
audience https://api.liminalkeys.com/t/<tenant-id>.
Account settings
Linked sign-in methods and explicit account linking live under Account settings,
opened from the avatar menu in the top bar (#profile).
Liminal Keys never links providers automatically — you confirm each connection.
Platform (Liminal Keys operators)
Accounts with the Liminal Keys platform-administrator role see an additional Platform view for customer tenants, beta-ops metrics, and payment/entitlement status — including which tenants are still on open beta versus in the 60-day conversion grace after an end-beta notice. This is an operator surface, not a customer self-serve feature.
Typical admin path
Console navigation follows this configuration flow (Overview stays the default landing page):
- Onboard an identity (import, generate + complete, or self-signed for testing)
- Register agents under AI agents and store API keys
- Add policy rules (subjects, optional approval, optional window) and Apply policy
- Configure CI & automation trusts and/or enroll Macs under Devices
- Invite users or sync directory subjects under Users & groups when rules need them
- Watch Overview metrics and Sign audit for denials and successful signs