Access starts with permission
Being signed in does not allow every action.
Setting up access and using a control are different steps. The actual permission determines which action is allowed and when.
The link starts setup
The setup link opens the intended booking access flow. It does not authorise controls on its own. A confirmation code is sent to the stored booking email address.
Confirmation establishes a session. This guest flow does not require a personal account, and setup can be completed in a browser.
Permission defines the scope
A grant concerns specific controls, actions and time windows. It belongs to the relevant booking or an independent order.
A session can remain active after a stay without keeping the previous control rights. Current permission is what matters whenever a control is used.
Shared stays remain limited
Travelling companions can set up their own sessions for the same stay and also need confirmation through the booking email address. This does not automatically grant future stays.
Guests do not become administration users either. Workspace editing permissions remain separate from personal permissions to operate controls.
An everyday example
The stay ends, the session remains
A guest used the heating control during their stay. After the permission window ends, they can no longer operate it even if their browser remains signed in.
Good to know
Your questions, answered.
Is a forwarded setup link enough?
No. Independent confirmation using a code sent to the stored booking email address is also required.
Does access automatically include door permissions?
No. Only explicitly approved and technically supported controls are available.
Explore what connects