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

# Connect dormakaba Exos 9300 with anny

> Automate time-limited access to your dormakaba Exos 9300 doors for bookings and community memberships.

[dormakaba Exos 9300](https://www.dormakaba.com/de-de/angebot/produkte/systemloesungen-zutritt-und-zeit/zutrittskontrollloesungen-fuer-grossunternehmen/kaba-exos-9300-basissystem--ka_500000) is an access control solution for large enterprises and complex buildings. With the integration, anny can automatically grant time-limited access to Exos locks for bookings and community memberships.

With dormakaba Exos 9300 in anny, you can:

* Automatically create booking-based access with a time buffer before and after the booking
* Assign community members permanent access to specific locks
* View access status and PIN codes directly in the booking detail view

The integration is mainly suitable for operators of large buildings or campus environments who control their access management via dormakaba Exos 9300 and want to automate bookings through anny.

<Info>
  Available from the Professional plan.
</Info>

## Typical use cases

| Use case                               | Description                                                                                                                                                                 |
| :------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Conference rooms in a building complex | **After booking, customers automatically receive a time-limited access link plus PIN.** Reception and the facility team no longer have to hand out keys or cards manually.  |
| Community access for tenants           | **Members of a community receive permanent access to defined doors.** Permissions are controlled centrally via anny, without creating individual access in the Exos system. |
| Event rooms with day bookings          | **Day guests only get access for the booked duration.** Access is removed automatically once it expires.                                                                    |

## How the Exos 9300 connection works

The integration uses the dormakaba Exos 9300 API. You authenticate with an API URL, a username and a password that you receive from your dormakaba contact. This authorizes anny to create and remove access (access rights with a time window and PIN) for the locks in your system.

If the credentials are changed or revoked on the dormakaba side, anny loses access. You then have to re-authenticate the integration in anny with the new credentials.

| Data                   | Direction        | Frequency                         |
| ---------------------- | ---------------- | --------------------------------- |
| Access (create/remove) | anny → Exos 9300 | Real time on booking/cancellation |
| Profiles (list)        | Exos 9300 → anny | During rule configuration         |

## Connect dormakaba Exos 9300

### Requirements

Before you connect dormakaba Exos 9300, make sure you have the following:

* API URL, username and password from your dormakaba contact or admin
* At least one lock that is set up and online in the dormakaba admin area
* anny Professional plan or higher

### Set up the connection

<Steps>
  <Step title="Authorize">
    From the menu bar, open **Integrations** and go to **Exos 9300**. Enter the **API URL**, the **username** and the **password**. Click **Verify authentication** to complete the process.
  </Step>

  <Step title="Configure">
    Create rules for booking-based or community-based access:

    1. Click **Add** to create a new rule
    2. Choose a **Resource** (for booking access) or a **Community** (for member access)
    3. Select the associated profiles via **Select profiles**
    4. For booking access, set **Access before the booking** and **Access after the booking** (each in minutes)
    5. Optionally activate **Transmit phone number and email** so that customers get mobile access via smartphone instead of a PIN
  </Step>
</Steps>

As soon as the connection is active, access is created automatically for new bookings and removed on cancellations.

<Tip>
  You can edit or delete existing rules via the **three dots** to the right of the rule.
</Tip>

### Settings & options

| Setting                         | Description                                                                                                                                                                              |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Access before the booking       | Minutes the access is active before the booking starts                                                                                                                                   |
| Access after the booking        | Minutes the access stays active after the booking ends                                                                                                                                   |
| Profiles                        | One or more Exos profiles per rule                                                                                                                                                       |
| Transmit phone number and email | Optional: if this switch is active, anny transmits the phone number and email of the booking person to Exos 9300 so they get mobile access via smartphone. In this case no PIN is issued |

### Activation history

In the integration settings, you can view the **activation history**. All created and removed access entries are listed there chronologically.

## Booking process for customers

Here is how your customers experience the integration:

<Steps>
  <Step title="Book a room">
    Customers book a resource through anny.
  </Step>

  <Step title="Receive an access link">
    anny automatically generates an individual access link plus PIN and sends both in the booking confirmation by email.
  </Step>

  <Step title="Open the lock">
    Customers open the **link from the email**, enter the **PIN** and click **Login**. There they see the access entries that belong to the booked resource.
  </Step>
</Steps>

## View access in the admin area

In the **booking detail view**, active and inactive access entries are shown. Click an access entry to view details:

| Status      | Meaning                                                                                                                                           |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scheduled   | The access is reserved and will be created shortly before the appointment. You see this status for future appointments and for recurring bookings |
| In progress | The access is being set up. For single bookings this is only a brief moment                                                                       |
| Successful  | The access is active and customers can operate the lock within the defined period                                                                 |
| Removed     | The access was removed by the system or an admin                                                                                                  |

<Tip>
  Via the **three dots** in the access detail view, you can navigate to the **integration settings** in anny.
</Tip>

## Limitations

The dormakaba Exos 9300 integration does not support:

* Remote open (opening the door at the push of a button from within anny): customers use the access link plus PIN instead
* Bundled access per order: anny does not combine several bookings of one order into a single access, but creates access per booking
* Self-service credential generation: API credentials must be provided by the dormakaba contact

## Disconnect

<Warning>
  If you want to keep existing access credentials but stop new ones from being created, deactivate the integration. If everything should be reset and deleted, delete the integration.
</Warning>

You can do both under **Integrations**: deactivate via the **toggle** in the top right, delete via the **three dots** → **Delete**.

## FAQ

<AccordionGroup>
  <Accordion title="Which hardware is compatible with Exos 9300?">
    You find all information about supported hardware on the [dormakaba website](https://www.dormakaba.com/de-de/angebot/produkte/systemloesungen-zutritt-und-zeit/zutrittskontrollloesungen-fuer-grossunternehmen/kaba-exos-9300-basissystem--ka_500000). anny communicates via the Exos 9300 API; hardware compatibility is determined by dormakaba.
  </Accordion>

  <Accordion title="How many access entries are created per booking?">
    anny creates a separate access entry for each profile selected in the rule. If customers book several rooms in one order, each booking gets its own access entries. A whole order is not combined into a single access entry.
  </Accordion>

  <Accordion title="What happens on a cancellation?">
    When the booking is cancelled, the access is removed automatically. The status changes to "Removed" and customers can no longer operate the lock.
  </Accordion>

  <Accordion title="When do customers get their access for recurring bookings?">
    For recurring appointments and appointments booked far in advance, the access is not created immediately but about 48 hours before the respective appointment. Until then it has the status "Scheduled" and no PIN is available yet. Single bookings receive their access immediately.
  </Accordion>

  <Accordion title="Can customers use access via the Kaba Exos app?">
    Yes. If you activate the **Transmit phone number and email** switch in the rule, anny sends the phone number and email of the booking person to Exos 9300. Customers then get mobile access via the Kaba Exos app instead of a PIN.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Access stays in the 'In progress' status">
    The lock may be offline or unreachable. Check in the dormakaba admin area whether the lock is online and has an active connection to the Exos infrastructure.
  </Accordion>

  <Accordion title="Authentication fails">
    The API credentials are invalid. Contact your dormakaba contact to get the correct values for API URL, username and password.
  </Accordion>

  <Accordion title="No access created despite a successful booking">
    Check whether an active rule exists for the booked resource. Also check in the activation history whether an error was logged.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> UI path: menu bar → Integrations → Exos 9300. Rule types: "Access through bookings" (resource) and "Access through communities" (community).
>
> Distinction from the other dormakaba integrations: Exos 9300 is the on-premise variant. anny connects to the URL of the customer's own Exos server. Auth fields: **API URL** (on-premise base URL), **username**, **password** (HTTP Basic, from the dormakaba contact, no self-service). Resivo and Exivo, in contrast, are cloud services (fixed cloud address). The selectable locking units are called **"Profiles"** in Exos (field "Select profiles"), "Components"/"Sites" in Exivo/Resivo. Do not mix the terminology. All three share the same access substructure.
>
> Rule fields: **Select profiles** (several possible), **Access before the booking** / **Access after the booking** (minutes), switch **Transmit phone number and email**. If the switch is active, no PIN is issued; phone number and email come from the booking (not from the rule) and the guest gets mobile access via smartphone. The switch can only be saved/activated if all services of the resource require a phone number. There is no configurable PIN field; the PIN comes automatically from the Exos system.
>
> Behavior: only accepted bookings with a customer receive access (no requests, no blockers). One access is created per selected profile per booking (several profiles = several access entries); an order is not bundled. Single bookings: immediately. Recurring/future bookings: scheduled, created about 48 h before the appointment, status "Scheduled" until then. A time change updates the existing access, a resource change recreates it, a cancellation removes it (removed at the Exos system). One rule per resource (a duplicate is blocked on save). Rules on a parent resource also apply to sub-resources.
>
> Community: access permanent (no end date in anny, 3-year duration at the Exos system). Button "Create missing access rights for existing community members" for retroactively catching up.
>
> Status labels: Scheduled, In progress, Successful, Failed, Removed. The booking detail area is called "Smartlock access". There is no external provider link ("View access at provider" is missing for Exos), only navigation to the integration settings. Activation history in the integration settings. No anny-native remote open. Plan: Professional (feature INTEGRATIONS\_SMART\_LOCKS).
>
> Disconnect: menu bar → Integrations → Exos 9300 → toggle (deactivate, existing access remains) or three dots → Delete (resets in anny).