> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/my-devices.md).

# Devices and privacy

Pair your phone with the OpenIAM Authenticator app so it can approve your sign-ins, and remove phones you no longer have.

Some organizations ask you to register the phone you use to approve sign-ins. Registering it pairs the **OpenIAM Authenticator** app on that phone with your account, so OpenIAM knows the phone is genuinely yours and can send sign-in requests to it.

Open **My Devices** from your account menu → **Devices & Privacy → My Devices**.

If you have none registered, the page reads *"No devices registered"*.

## Registering a device

You need your phone and your computer in front of you at the same time: the computer shows a code, the phone scans it and shows you a number, and you type that number back into the computer.

Before you start, install the **OpenIAM Authenticator** app on your phone from its app store — it appears as *OpeniamAuthenticatorApp* on the phone — and allow it to show notifications when it asks. A sign-in request arrives as a notification, so a phone that declines never sees one.

{% stepper %}
{% step %}
**Choose Register New Device.**

The page is titled *"New Device Registration"* and shows a QR code with a **Token** field beneath it.
{% endstep %}

{% step %}
**Scan the code from inside the OpenIAM Authenticator app.**

On your phone, open the app, choose **Register Device** — or **Scan QR code**, if the app has no accounts yet — and point the camera at the code on your computer screen. Do not use your phone's ordinary camera app: it cannot register the device, and at best opens a web page.
{% endstep %}

{% step %}
**Read the PIN from the phone.**

A moment after the scan, the app shows a six-digit PIN under *"Please Enter the following PIN on the verification screen"*.
{% endstep %}

{% step %}
**Type the PIN into the Token field and confirm.**

Your computer shows *"Device Registered Successfully"*, and so does the phone. The device appears in your list with its **Manufacturer**, **Brand** and **Model** filled in by the app, and **Active** ticked.
{% endstep %}
{% endstepper %}

From now on the app asks for your phone's fingerprint, face or passcode before it opens. If the phone has no screen lock, set one — the app will not open without it.

## Activating and deactivating

A registered device can be switched off without being deleted:

* **Deactivate** it — *"Device Deactivated"* — and it stays on your list but no longer receives sign-in requests. This is what you want when you have mislaid a phone but expect it back.
* **Activate** it again — *"Device Activated"* — when you have it.

## Removing a device

Select it and delete. You are asked *"Are you sure you want to delete the selected device?"*, because it cannot be undone — you would have to register the device again from scratch.

Remove it here rather than only deleting the account in the app: removing it from **My Devices** tells the phone to forget the pairing too, so the account disappears from the app on its own. Deleting the account on the phone alone leaves the device on your list, and sign-in requests keep going to it.

Remove a device when you replace your phone, hand back a company device, or lose one permanently. A new phone, or the app reinstalled on the same phone, has to be registered again from the start.

{% hint style="warning" %}
If a device is lost or stolen, deactivate or remove it **immediately**, then change your password. A registered phone can approve sign-ins to your account, so it is worth treating with the same urgency as a lost badge.
{% endhint %}

## If registration fails

* You closed the page before typing the PIN — start again from **Register New Device** and scan the new code. If the phone had already scanned the old one, it is on your list with **Active** not ticked: remove that entry first.
* *"Device registration failed."* on your computer after typing the PIN — check the digits against the phone, and type them into the same window that showed the code. If in doubt, start again from **Register New Device**.
* Your phone shows *"Device already registered"* after scanning — that phone is already on your list. Check before adding a duplicate.
* Your phone shows *"Error Contacting Server"* — it could not reach your organization's sign-in service. Check that the phone is online and try again; if it keeps happening, contact your help desk.
* *"Unable to register device. Please try again later."* on the phone, or *"Unable to delete device."* on your computer — the service could not complete the request. Wait a little and retry; if it persists, contact your help desk.
* The app will not open afterwards and says *"Error Unlocking Device"* — your phone has no screen lock. Set a passcode or fingerprint on the phone, then open the app again.

None of these means you have done anything wrong.


---

# 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://docs.openiam.com/end-user-guide-for-selfservice/my-devices.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.
