Skip to main content
Registration keys authorize new machines to join your organization. Keys can be configured for single or multiple registrations.
Device Settings page showing an Update Channel card set to Production and a Device Registration Keys table listing Engineering Team (10/20) and CI Runners (3/5) keys, each with an rk_live prefix, usage count, Never expiry, and Active status.

Device Settings: the update channel plus the device registration keys table with prefix, usage, expiry, and status.

Registration keys are optional for desktop users. If you install the desktop app, you can register a machine by launching it and signing in (or signing up), with no key required. See keyless desktop sign-in below. Keys remain the path for headless, fleet, and CI installs where no one signs in interactively.

​
When You Need a Key

Keyless desktop sign-in is the recommended first-run flow for individual developers. The rest of this page covers keys for the headless, fleet, and CI cases.

​
Key Format

Registration keys use the prefix rk_live_ followed by a random string:

​
Creating a Registration Key

Registration keys are managed separately from API keys. Navigate to Devices > Settings (/agent-control/settings).
1

Click Create Key

Fill in the key details:
2

Copy the key

The full key is shown once. Copy it immediately: you won’t be able to see it again.
3

Share with your team

Distribute the key securely to developers who need to install the agent.
Registration keys are managed at Devices > Settings (/agent-control/settings), not in Org Settings > API Keys. They are a separate concept from dashboard API keys.

​
How Registration Works

When a developer installs the Turen agent with a registration key:
  1. The agent generates a unique machine fingerprint
  2. It sends the fingerprint and registration key to the Turen API
  3. The API validates the key, creates an agent record, and returns a permanent agent secret (as_live_)
  4. The key’s usage count is incremented
  5. The agent stores the agent secret securely for future authentication

​
Key Properties

​
Managing Keys

From Devices > Settings (/agent-control/settings), you can:
  • View all keys: See key name, description, prefix, usage count (current / max), expiry, and status
  • Revoke a key: Prevent any further registrations with this key
  • Delete a key: Permanently remove a revoked key
For large deployments, create a key with a high max registration count rather than generating individual keys for each machine.