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

# Kisi Setup Guide

> Connect your Kisi organization to Seam using a Kisi API key.

## Overview

This guide walks you through connecting your Kisi organization to Seam as an access control system. Seam authorizes against Kisi using an API key that you generate in the Kisi dashboard. Your Kisi controllers and doors must already be set up and online in Kisi before you begin.

***

## Step 1: Generate a Kisi API Key

Seam connects to Kisi with an API key rather than a login email and password.

To generate a key:

1. Sign in to the [Kisi dashboard](https://web.kisi.io/).
2. Go to **My Account → API**.
3. Create a new API key and copy it.

For detailed instructions, see Kisi's guide on [generating an API key](https://docs.kisi.io/dashboard/account/generate_api_key/).

<Info>
  Generate the API key from an account that is an **organization owner**, so
  Seam has permission to see and unlock all of the locks you want to manage. A
  key inherits the permissions of the user who created it.
</Info>

***

## Step 2: Connect to Seam via Connect Webview

1. Open the [Connect Webview](/core-concepts/connect-webviews) provided by your application.
2. Select Kisi as the provider.
3. Paste your Kisi **API key** into the field and submit.
4. Once authorized, your Kisi organization appears as an access control system in Seam, and each door appears as an entrance.

***

## Step 3: Verify the Connection

After connecting, verify that your Kisi organization appears as an access control system and that its doors appear as entrances with unlock capability. Doors that have geofence or reader-proximity restrictions enabled in Kisi display a warning, because remote unlocks against those doors may be rejected.

***

## Troubleshooting

### Authorization fails in Connect Webview

Confirm that you pasted a valid, active Kisi API key. Keys created in the Kisi dashboard can expire after a period of inactivity — if authorization fails, generate a fresh key and try again. Make sure the key belongs to an organization owner so it can access all of your doors.

### Entrances not appearing after authorization

Ensure the doors exist in your Kisi organization and are assigned to a place. Seam lists the doors that the API key's user can access, so a key from a user with limited permissions may not see every entrance.

### Entrance shows as offline

Check that the Kisi controller for that door is powered on and connected to the network. Seam can only unlock doors whose controllers are online.

### Unlock is rejected

If a door has geofence or reader-proximity restrictions enabled in Kisi, remote API unlocks may be denied. Review the door's restriction settings in the Kisi dashboard.