> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tappify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Activating devices

> Pair a device to an app from the dashboard, and manage devices that are already paired.

Pairing is how a device goes from "just another install of the app" to "this device can see
and drop review comments." It's always started from the dashboard, by someone already on
your team.

## Pair a device

<Steps>
  <Step title="Open Review on this device">
    From your app's page on the Tappify dashboard, open the Review tab and click
    **Review on this device**. This shows a QR code and a tappable activation link.
  </Step>

  <Step title="Open the link on the device you want to pair">
    Scan the QR code with the device's camera, or tap the link if you're already on the
    device (e.g. opening it in Messages or Notes). This opens your app directly via the URL
    scheme registered in [the quickstart](/sdk/quickstart).
  </Step>

  <Step title="Done">
    The app exchanges the link for a paired session and the pill appears. No further sign-in
    is needed on that device again unless it's later revoked.
  </Step>
</Steps>

<Note>
  The QR code and link refresh automatically roughly every 50 seconds while the dialog is
  open, so a code that's been on screen a while is still safe to scan.
</Note>

## The 60-second link lifetime

Each activation link is single-use and expires 60 seconds after it's minted. This is
deliberate — it keeps a screenshotted or forwarded link from being usable later. If a link
has gone stale by the time it's opened, the app shows one neutral toast and the pairing
simply doesn't complete; mint a fresh one from the dashboard and try again. See
[Troubleshooting](/sdk/troubleshooting#activation-link-doesnt-work) for what that looks
like from the device side.

## Internal builds: Sign in with Tappify

On internal builds (TestFlight or a development build — see
[Gating modes](/sdk/gating-modes) for the exact definition), if your app's gating mode
allows internal review, the SDK can show a "Sign in with Tappify" affordance before anyone
has paired. Tapping it opens a Tappify sign-in flow in-app; if the reviewer is already
signed in to Tappify on the web, this is one tap. This path only ever appears on internal
builds — live, App Store builds never show anything before a device is paired.

## Revoking devices

From the same Review tab, the **Devices** list shows every device paired to the app, and
each row has a **Revoke** button. Revoking a device:

* Removes that device's ability to see or post comments on this app.
* Takes effect on the device's next check-in (app launch or foreground), not instantly —
  see [Gating modes](/sdk/gating-modes#how-fast-a-change-takes-effect) for the exact
  latency bound.
* If the device used [team-wide pairing](/sdk/team-wide-pairing), also revokes its access
  to every other app that shared the pairing.

<Warning>
  Revocation isn't instant. A device that's mid-session can keep working for a short window
  after you revoke it — see [Gating modes](/sdk/gating-modes#how-fast-a-change-takes-effect)
  for the bound. If you need to be certain a specific person can no longer see review
  comments, revoke their device and confirm from the dashboard that it no longer shows as
  active.
</Warning>