> ## 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 Glutz eAccess with anny

> With Glutz eAccess, create time-limited PIN access for the matching door automatically per booking.

[Glutz eAccess](https://www.glutz.com) is an access system that controls doors via digital locking components and PIN codes. anny connects to your local Glutz eAccess server for this. With the integration, anny automatically creates a time-limited access with an individual PIN code for the matching door on every booking.

With Glutz eAccess, you can do the following in anny:

* Automatically create a time-limited access with an individual PIN code per booking
* Link anny resources to one or more Glutz access points through rules
* Adjust access automatically on booking changes and remove it again on cancellations
* Open doors via Remote Open directly from the anny booking view or homepage

The integration is especially handy when you rent out rooms or resources with a Glutz locking system and want to offer your customers automated, time-limited access without a manual key handover.

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

## Typical use cases

| Use case                           | Description                                                                                                                                                                                      |
| :--------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Unlock meeting rooms automatically | **Access exactly within the booked time window.** When a meeting room is booked, the booking person automatically receives a PIN for the matching door, valid including lead and follow-up time. |
| Coworking and office spaces        | **Keyless access without a front desk.** Customers enter booked spaces on their own via PIN, without any manual key handover.                                                                    |
| Short-notice rebookings            | **Access stays up to date automatically.** If the booking time changes, anny automatically adjusts the access window in Glutz.                                                                   |

## How the Glutz eAccess connection works

The connection is set up using credentials, not OAuth. You store the **API base URL** (the server address of your Glutz instance) as well as the username and password of a Glutz user. anny then authenticates with your running Glutz eAccess server and is allowed to create, update and remove access there.

As soon as a resource with a matching rule is booked, anny creates a separate access in Glutz for exactly that booking and assigns an individual PIN code. No personal data is stored in Glutz, only the booking number as a reference.

For single bookings, anny creates the access immediately. For recurring bookings, anny prepares each appointment individually shortly before the access starts: until then the access stays at **Scheduled** and is created about two days before the appointment.

If you change the stored password or deactivate the Glutz user, anny loses access and can no longer create new access. In that case, update the credentials in the integration.

| Data                            | Direction    | Frequency                                    |
| ------------------------------- | ------------ | -------------------------------------------- |
| Access (create, update, remove) | anny → Glutz | On booking creation, change and cancellation |
| PIN codes                       | anny → Glutz | On booking creation                          |

## Connect Glutz eAccess

### Requirements

Before you connect Glutz eAccess, make sure you have the following:

* Admin rights with access to the **Integrations** in anny
* A running Glutz eAccess server
* The **API base URL** (server address) of your Glutz instance
* Username and password of a Glutz user with sufficient rights
* Access points (doors) set up in Glutz
* The code length defined in Glutz, which you carry over into anny

### Set up the connection

<Steps>
  <Step title="Open the integration">
    Open the **Integrations** from the **menu bar** and select **Glutz eAccess**.
  </Step>

  <Step title="Authenticate">
    Enter the **API base URL** (your Glutz server address), **username** and **password** and click **Check authentication**. anny then connects to your running Glutz eAccess server.
  </Step>

  <Step title="Create rules">
    Use a **rule** to link an anny resource to one or more Glutz **access points**. Per rule, define **Access before the booking** and **Access after the booking** and optionally enable **Use remote opening**.
  </Step>

  <Step title="Set the code length">
    Under **PIN codes**, enter the **code length (digits)** you have configured in Glutz. Allowed are 4 to 8 digits (default 6). The value in anny must match the setting in Glutz.
  </Step>

  <Step title="Check the connection">
    In the **Integrations**, check whether Glutz eAccess is shown as active.
  </Step>
</Steps>

Once the connection is active and a rule applies, anny automatically creates a time-limited access with a PIN on every matching booking.

<Tip>
  For **Access before the booking** and **Access after the booking**, plan enough buffer so customers can enter shortly before the booking start and leave the room shortly after the booking end.
</Tip>

### Settings & options

| Setting                   | Description                                                                                          |
| ------------------------- | ---------------------------------------------------------------------------------------------------- |
| Access before the booking | Minutes before the booking start from which the access is active.                                    |
| Access after the booking  | Minutes after the booking end up to which the access stays active.                                   |
| Use remote opening        | Enables opening the door at the push of a button from anny.                                          |
| Code length (digits)      | Length of the generated PIN code (4 to 8 digits, default 6). Must match the setting stored in Glutz. |

### Remote Open

With the Remote Open function, customers can open door locks at the push of a button: directly via the anny homepage or the booking view. This makes access possible even without entering a PIN at the access point. Enable **Use remote opening** per rule so the button appears for the linked access points. The button can only be used within the access window (booking time plus lead and follow-up time).

| Location                 | Where do you open the door?                                                                               |
| ------------------------ | --------------------------------------------------------------------------------------------------------- |
| Email                    | The **Open** link in the booking email leads to the booking page in the browser, where the button appears |
| Booking page (customers) | **Unlock door** button in the customers' booking view                                                     |
| Booking overview (admin) | **Unlock lock** button in the booking overview in anny                                                    |

## Limitations

The Glutz eAccess integration does not support:

* Access to doors that are not set up as an access point in Glutz.
* Automatic access without a matching rule: without an assignment of resource to access point, no access is created.
* Storage of personal data in Glutz: only a booking reference is passed for assignment.

## 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="How long is the PIN code?">
    The **code length (digits)** is configurable (4 to 8 digits, default 6). You define in Glutz how long the code may be and enter the same value in anny. Both settings must match.
  </Accordion>

  <Accordion title="Do my customers receive the PIN automatically?">
    Yes. As soon as a matching booking is created, anny automatically generates an individual PIN for the associated door and the booked time window. For recurring bookings, the PIN is generated per appointment only shortly beforehand, about two days before the access starts.
  </Accordion>

  <Accordion title="What happens when a booking is changed or cancelled?">
    On a time change, anny automatically adjusts the access window. On cancellation or deletion, anny removes the access including the PIN from Glutz again.
  </Accordion>

  <Accordion title="Can I unlock multiple doors per resource?">
    Yes. Per rule, you can link a resource to one or more Glutz access points.
  </Accordion>

  <Accordion title="Which data does anny store in Glutz?">
    anny passes no personal data to Glutz. Only a booking reference is used for assignment.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The PIN does not work yet">
    Check the **Access before the booking** setting and the booking start. The access is active only from the booking start minus this lead time. Also check whether the resource is correctly assigned to an access point in a rule. For recurring bookings, the access is also created only about two days before the appointment.
  </Accordion>

  <Accordion title="The PIN does not work after an extension">
    Check whether the booking was actually updated and the change went through in Glutz. anny only adjusts the access window if the booking time was changed successfully.
  </Accordion>

  <Accordion title="The PIN opens the wrong door">
    Check the rule mapping. Verify whether the resource is assigned to the correct Glutz access point.
  </Accordion>

  <Accordion title="The access is still active after a cancellation">
    Check whether the booking was cancelled or deleted correctly and whether the connection to Glutz is active. anny can only remove the access when the connection is active.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> On-premise, NOT cloud: anny connects to a local Glutz eAccess server. The field is called "API base URL" in the UI (tooltip: "Base URL of your local Glutz eAccess server", placeholder e.g. [https://your-server:8332](https://your-server:8332)). Phrasings like "Glutz Cloud" are wrong.
>
> UI path setup: menu bar → Integrations → Glutz eAccess → enter API base URL, username, password → button "Check authentication". Then section "PIN codes" (code length) and rules ("Access through bookings"). Disconnect: Integrations → Glutz eAccess → deactivate toggle in the top right → three dots → Delete.
>
> Authentication: basic auth (API base URL + username + password), NOT OAuth. Distinct from OAuth locks like Nuki.
>
> Code length: UI label "Code length (digits)" in the "PIN codes" section, allowed 4-8, default 6. Must be identical to the Glutz setting. Per booking one own Glutz user (label "anny booking-number") with a random PIN of this length.
>
> Rule fields (shared smart lock interface): "Access before the booking" / "Access after the booking" (padding), "Use remote opening" (Remote Open switch), "Access points" (locks). Access validity = booking time + lead + follow-up.
>
> Remote Open can be enabled per rule; button only active within the access window. Labels: email link "Open" (→ booking page in the browser), customer booking view "Unlock door", admin booking overview "Unlock lock".
>
> Series vs. single: single booking → access immediately + separate access notification. Recurring booking → per appointment status "Scheduled", creation about 48 h before the access starts, NO separate notification.
>
> Trigger conditions: only accepted bookings with a customer; blockers and requests trigger nothing. A rule on a parent resource also applies to sub-resources (a more specific rule takes precedence). Only one rule per resource (a duplicate is rejected on saving).
>
> Status values of an access: In progress, Scheduled, Unconfirmed, Successful (label "Successful", not "Successfully created"), Failed, Not authorized, Cleaning up, Removed.
>
> No hard limits for simultaneous/future access per access point (unlike Nuki with 200). Expired access is NOT cleaned up automatically at Glutz; the PIN is invalidated by the expiry date (validTo), the Glutz user remains.
>
> If-then: booking created → access + PIN created. Booking time changed → only access window adjusted, PIN stays the same. Booking cancelled/deleted → Glutz user + PIN actively deleted.
>
> Privacy: no personal data in Glutz, only the booking number as a reference.
>
> Rule requirement: without a rule (resource ↔ access point) no automatic access. Access points must exist in Glutz beforehand.
>
> Available from the Professional plan (feature INTEGRATIONS\_SMART\_LOCKS; plan boundary not verifiable from the code). Active/GA by default via env flag. Main use case: room booking. Related articles: Smart Locks overview, Nuki, SaltoKS, Dormakaba Exivo/Resivo.