Skip to main content
Glutz eAccess 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.
Available from the Professional plan.

​
Typical use cases

​
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.

​
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

1

Open the integration

Open the Integrations from the menu bar and select Glutz eAccess.
2

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.
3

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.
4

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.
5

Check the connection

In the Integrations, check whether Glutz eAccess is shown as active.
Once the connection is active and a rule applies, anny automatically creates a time-limited access with a PIN on every matching booking.
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.

​
Settings & options

​
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).

​
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

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.
You can do both under Integrations: deactivate via the toggle in the top right, delete via the three dots → Delete.

​
FAQ

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.
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.
On a time change, anny automatically adjusts the access window. On cancellation or deletion, anny removes the access including the PIN from Glutz again.
Yes. Per rule, you can link a resource to one or more Glutz access points.
anny passes no personal data to Glutz. Only a booking reference is used for assignment.

​
Troubleshooting

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.
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.
Check the rule mapping. Verify whether the resource is assigned to the correct Glutz access point.
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.