Domain Dependencies

Dashboards & Management

Accessing Interact Applications

Why

  • The Multiroom Dashboard’s browser-based interface enables hotel staff to serve guests, and monitor and manage the system.

How

  • The dashboard and interact APIs are served locally on-premise as a web service, accessible via a domain gateway.

  • A firewall rule needs to allow users on the admin network to access the Interact application server, which provides the webservices over HTTPS.

  • Only the Multiroom System Manager domain gateway URL is required to be trusted on client PCs and should be added to the network’s DNS to allow staff access.

    https://myhotel.example.com is the only address that is externally accessible via the local network. After installation you can find the gateway URL in Windows IIS. This is the URL for all dashboard, API, and WebSocket connections. The gateway then routes requests to the individual APIs, as in the example table below:

    Domain IP:Port Local/Remote

    https://myhotel.example.com

    [SM server IP address]:443

    Remote

    https://api.example.com

    127.0.0.1:443

    Local

    https://usermgmt.example.com

    127.0.0.1:443

    Local

    https://dashboard-local.example.com

    127.0.0.1:443

    Local

    https://energyapi.example.com

    127.0.0.1:443

    Local

    https://dynalitecontrolapi.example.com

    127.0.0.1:443

    Local

    https://publicapi.example.com

    127.0.0.1:443

    Local
Requirements checklist

  • Firewall access opened

    • Interact Server <> Staff PCs

    • Port 443

  • Authorisation

    • For users to access the dashboard they will need:

      • An @[hoteldomain.com] user account with valid password (see LDAP (Active Directory)).

      • A user profile assigned within the dashboard by an authorised user.

  • Versions

    • We maintain support for modern web browsers including Chrome, Edge, and Firefox.

LDAP (Active Directory)

User Authentication

Why

  • Multiroom System Manager uses LDAP (Active Directory) to allow authorized users to log in with their existing user@[hoteldomain.com] username and password.

  • This ensures consistent corporate password rule compliance and easy login for staff using the Multiroom Dashboard and reporting tools.

  • Within System Manager, each user account is linked to one or more profiles to determine access rights (different modules, read/write permissions, etc.) once they are logged in. These rights and profiles are managed by authorized users.

How

  • System Manager requires permission to connect to the hotel’s LDAP server (a firewall rule allows connections from the application server).

  • System Manager requires its own user@[hoteldomain.com] account, authorized to connect to, query, and authenticate users with the LDAP server.

Requirements checklist

  • Firewall access opened

    • SM Server <> LDAP Server

    • Port 636 (LDAPS) or 389 (no encryption, StartTLS, or LDAP)

    • Interact acts as a client of the LDAP server

  • Authorised User Account

    • user@[hoteldomain.com] account.

    • Authorisation to access and query the LDAP server to authorise users

    • Suggested that the account password does not expire

SMTP / Email Server

Email Notifications and Alerts

Why

  • Multiroom System Manager sends emails to notify when:

    • New user accounts are granted access permission.

    • Alerts such as room exceptions are detected in rooms or in the system.

How

  • System Manager requires permission to connect to the hotel’s SMTP server (a firewall rule allows connections from the application server).

  • System Manager requires a user@[hoteldomain.com] account authorized to connect to and send emails through the SMTP server.

Requirements checklist

  • Firewall access opened

    • SM Server <> SMTP Server

    • Port 465 (or other if configured differently on the hotel network)

    • SM acts as a client of the SMTP server

  • Authorised User Account

    • user@[hoteldomain.com] account.

    • Authorization to send emails through the SMTP server.

    • Suggested that the account password does not expire.

    • The email account is outbound only, so an out-of-office message can be created to explain that messages will not be read in case any users try to reply to a notification.