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

# Mobile SDK Keys

> Issue and revoke the single SDK key your app's OneS1ght SDK uses, and set its access scope.

<Info>
  This page is available to **Manager** and above only (permission `manage` — Owner or Manager).
</Info>

## What are Mobile SDK Keys?

**Mobile SDK Keys** is the screen where you issue and revoke the **API key** used by the OneS1ght SDK embedded in your app.
The key is a **single key** in the `ock_sdk_...` format and appears masked in the list. There is no development/production environment split.
For how to wire the key into your app, see the integration guide in the [Mobile SDK](/en/sdk/overview) section.

## Access scope

Choose an access scope when issuing a key.

| Scope                                                | Description                                                                                 | Badge       |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------- | ----------- |
| Full access (measure at all positioning connections) | Measures at all positioning connections (aliases). (`scope_mode: all`)                      | All         |
| Measure only at specific aliases                     | Measures only at the selected positioning connections (aliases). (`scope_mode: restricted`) | N alias(es) |

<Note>
  **Positioning connections (aliases)** are managed in the positioning management screen. See [Positioning Data](/en/locator/positioning-data).
</Note>

## Issuing a key

<Steps>
  <Step title="Issue API key">
    Click **Issue API key**.
  </Step>

  <Step title="Choose access scope">
    Choose **Full access** or **Measure only at specific aliases**. If you choose specific aliases, select the positioning connections (aliases) allowed to measure.
  </Step>

  <Step title="Copy the one-time key">
    The full key value is shown **only once**, right after issuing. Copy it and store it somewhere safe. Once you close the window, you cannot view the full value again.
  </Step>

  <Step title="Apply it in your app">
    Set the copied key in the SDK. See the [Mobile SDK integration guide](/en/sdk/overview) for details.
  </Step>
</Steps>

<Warning>
  The full key value is shown only once, right after issuing; afterward it is masked and cannot be viewed again. Be sure to store it securely.
</Warning>

## Managing keys

| Item         | Details                                  |
| ------------ | ---------------------------------------- |
| Key format   | `ock_sdk_...` (shown masked in the list) |
| Access scope | All / N alias(es)                        |
| Status       | Active / Revoked                         |
| Issued       | The date the key was issued              |

### Edit scope

You can change the access scope after issuing via **Edit scope** (All ↔ specific aliases, adjust allowed aliases).

### Revoke

An active key can be **revoked**. A revoked key **stops working immediately and cannot be restored** (a confirmation modal is required).

## Integration guide

<Card title="Mobile SDK integration guide" icon="mobile-screen" href="/en/sdk/overview">
  Learn how to integrate positioning in your app using the SDK key you issued.
</Card>

## Related

<CardGroup cols={2}>
  <Card title="Positioning Data" icon="plug" href="/en/locator/positioning-data">
    Connect positioning connections (aliases) and the real floor plan.
  </Card>

  <Card title="Areas" icon="draw-polygon" href="/en/locator/areas">
    Edit zones/points on the floor plan.
  </Card>
</CardGroup>