> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/security-governance/emergency-access/register-a-security-key-for-emergency-access.md).

# Register a security key for emergency access

This article describes how to register and manage a security key for Cerby Emergency Access.

{% hint style="info" %}
**Who can use this feature?**

* A workspace member assigned to emergency access, except **Guest Users** and **Login-Only** users
* Supported using the Cerby web app
  {% endhint %}

As a workspace member assigned to emergency access, you can register a security key so you can log in to your workspace if your identity provider becomes unavailable. You register your security key from a normal, identity-provider-authenticated session, before any outage occurs. You can register up to five security keys and remove any of them at any time.

## Requirements

This procedure requires the following:

* The enrollment email Cerby sent when you were assigned
* A FIDO2 or WebAuthn security key, and a browser and device that support it

## Register a security key for emergency access

To register a security key, you must complete the following steps:

1. Log in to your [Cerby](https://app.cerby.com/) workspace.
2. Open the enrollment email Cerby sent when you were assigned to emergency access.
3. Click the enrollment link. The **Set up your Cerby Emergency Access** page is displayed.
4. Click the **Add a key** card. A field to name your security key is displayed.
5. Enter a name for your security key in the **Name this key (optional)** field. This step is optional.
6. Click the **Register a security key** button. Follow the prompts from your browser or device to verify your security key with a PIN or biometric.

The security key is added to your list of registered keys.

{% hint style="warning" %}
A workspace member can register a maximum of five security keys. If you reach this limit, remove a key you no longer use before you register a new one.
{% endhint %}

To register another security key, click **Add another key** and repeat these steps. When you're finished, click **Done**.

Now you are done.

## Related articles

**Setup guides:**

* [Explore Cerby Emergency Access](/setup-and-admin/security-governance/emergency-access/explore-emergency-access.md)
* [Remove a registered security key](/setup-and-admin/security-governance/emergency-access/remove-a-registered-security-key.md)
* [Log in with emergency access](/setup-and-admin/security-governance/emergency-access/log-in-with-emergency-access.md)

**Troubleshooting:**

* [Troubleshooting: Emergency Access issues](https://help.cerby.com/tips-and-troubleshooting/troubleshooting/workspace-access/troubleshooting-emergency-access-issues)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.cerby.com/setup-and-admin/security-governance/emergency-access/register-a-security-key-for-emergency-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.