Settings

Settings holds what applies to a whole hotel. It needs the Admin area β€” see Areas and roles.

Features

Features are chosen per template β€” see Features & rooms. (The old Settings β†’ Property β†’ Features screen opens Features & rooms.) Phone pairing, the phone remote, the home screens and TV installation are always on.

Service package

Settings β†’ Property β†’ Service package shows what the site has. The basic package is always on: the TV app, Live TV channels and apps, the guest's phone, movies and hotel services, reservations and check-in, TV installation and its checks. Custom adds, per site, Room devices (IoT) β€” lights, temperature, curtains and the housekeeping panel from the building system. With it off, the IoT Manager, the device columns in Guest Operations β†’ Rooms, Room devices on the Dashboard and Room controls on the guest's phone are hidden, Room controls cannot be ticked in Features & rooms, and the 15-minute checks skip room devices. Turning it off keeps the devices and their setup. Only an admin can change it.

Integrations

Integrations has three tabs: Client API (keys for other companies' apps), PMS (the hotel's property management system) and Building systems (the room devices' building system). You need the Admin area.

Client API

The Client API tab is where a site administrator gives other companies' apps access to the site's rooms. It lists the API keys β€” one per partner β€” with when each was created and last used, and the base address of the Client API.

A key reaches every room of the site, so give each partner its own. Guests' phones do not use keys: they use the token they receive when they pair with the TV, which reaches only their room and stops working at check-out.

PMS and Building systems

These tabs connect the site to another company's system. Each tab has a sub-menu: Overview β€” every option with its status (and Switch on / off) β€” then one item per option (on the PMS tab: Local first, then OPERA, Apaleo, Mews, Guesty (planned) and Any PMS; on the Building systems tab: Schneider Electric, then the planned makers). A provider's item shows, once connected, its settings, test, webhook address, rooms and stays, and log; before that, what connecting needs and Connect.

Provider Kind State
Apaleo PMS Can be connected and tested
Mews PMS Can be connected, tested and synchronised (demo or production environment)
Guesty PMS Planned β€” short-term rentals and serviced apartments
Oracle OPERA Cloud (OHIP) PMS Can be connected, tested and synchronised β€” read every 5 minutes (no webhook)
Schneider Electric EcoStruxure Building systems Can be connected β€” each site with its own SE account; lights, curtains, thermostats and courtesy panels, connected step by step β€” see Connecting Schneider Electric
Legrand GRMS, Honeywell INNCOM Building systems Planned β€” the makers have no public cloud API; it needs their partner documentation

Only one PMS can be on at a time β€” two systems must not check the same rooms in and out. To try or move to another PMS, Switch off the current one (its settings, secrets and room links are kept) and connect the other; switch it back on later by switching the other off. Each PMS checks out only the guests it checked in.

Rooms and stays (Apaleo, Mews, OPERA)

Once an Apaleo, Mews or OPERA connection tests fine, its card shows Rooms and stays (below, Apaleo; Mews works the same way β€” see Mews and OPERA for what differs):

  1. Read rooms from Apaleo β€” reads the property's rooms. A room whose name is the same as a room number here is linked automatically β€” unless the PMS has more than one room with that name (then link it by hand). One list shows either Rooms or Room types (switch above it); Search and Show All / Linked / Not linked narrow it; link the others with the list next to each room (or leave them unlinked β€” nothing happens for them). A room you link by hand stays as you chose when the rooms are read again. Read again after adding rooms in Apaleo.
  2. Register webhook β€” asks Apaleo to send reservation events to this connection's webhook address.
  3. From then on, what happens in Apaleo reaches the linked rooms within seconds:
    • check-in β€” the guest's name and language go to the room (the TV restarts and greets the guest, the phone can pair), exactly as a check-in in Guest Operations β†’ Rooms;
    • check-out (or a cancelled / no-show reservation that was in the room) β€” the room is checked out: the TV restarts, the phone is disconnected and the room is reset (Do Not Disturb off, lights off, thermostat default);
    • room move β€” the old room is checked out and reset, the new room checked in. Each one is in the log with the reservation number. The event is re-read from Apaleo before anything is done, so an event that arrives twice or out of order does no harm.
  4. Sync now β€” compares the rooms here with the reservations in house in Apaleo and fixes any difference (for example events missed while the connection was off). Guests checked in from the console are left alone; only guests the PMS checked in are checked out by it. It also catches up on reservations: confirmed bookings arriving in the next 90 days get their stay and app link (or have their dates, room type and name updated), and a booking still shown as Booked here that Apaleo no longer lists as confirmed is read again β€” if it was canceled, a no-show or already checked out, it is closed (up to 50 such bookings per run; press again for more). The result reads, for example, Reservations arriving in 90 days: 11 β€” 2 new links, 1 closed. Running it twice changes nothing the second time.

Room types. Read rooms from Apaleo also reads Apaleo's room types (unit groups, for example Double) and lists them under Room types on the same card. Link each to a room type here β€” one with the same name is linked automatically, or pick + New room type to create one with Apaleo's name. Before check-in a reservation only has a room type, so this is what decides the template, channels and IoT choices a guest sees before arriving.

Mews

OPERA Cloud (OHIP)

The full setup guide β€” what the hotel and Oracle must provide, the steps, problems and testing β€” is OPERA Cloud (OHIP).

In Guest Operations β†’ Rooms a guest checked in by the PMS has a PMS tag. Check guests in and out in the PMS. A check-in or check-out from the console still works, but the PMS does not know about it, so the two disagree β€” and the PMS may change it back with its next event or Sync now (for example the PMS still shows the guest in house, and Sync now checks the guest back in). That is why Rooms warns you: a banner at the top says which PMS runs the check-ins, and the check-in window and the check-out confirmation of a room linked to the PMS say so again (check-out then asks you to confirm Check out here anyway). Rooms that are not linked to the PMS are checked in and out in the console as usual.

Connecting Schneider Electric

Settings β†’ Integrations β†’ Building systems β†’ Schneider Electric is a connection like a PMS: each site uses its own SE account. Press Connect Schneider Electric and enter what Schneider Electric gave the hotel for its EcoStruxure tenant β€” the client id and client secret (kept like a PMS secret: saved, never shown again), and only if SE gave other ones, the API address, sign-in (token) address and scope (empty uses SE's defaults). It needs the Admin area. Switch off stops the site reaching SE; the log shows each time SE was read.

A site without its own connection uses Provyl's platform account only if it is Not billed (our demo and pilot sites); every other site must connect its own before it can read SE or go Live. Step 1 has Disconnect for Provyl's account (Admin area, Admin): the site stops reading and controlling SE at once and Live rooms run as simulated; rooms, devices and the building stay saved. Reconnect Provyl's platform account undoes it. A site's own connection is removed with Remove (or paused with Switch off).

Below the connection, the site's rooms are connected in five steps; each shows βœ“ when it is done. Nothing in it writes to SE β€” it reads SE and records which room and device is which, and commands reach the building only once the site is Live. You need the Devices area (Operator; Admin for Live).

  1. SE account β€” which account the site uses (its own, or Provyl's platform account) with the settings in use β€” API address, sign-in address, scope and the client id (partly hidden); the secret is only shown as set β€” and that it can read SE: the number of buildings it sees. The result is in the connection's log and Last success; an error is shown as is (for example SE sign-in failed (401) β€” check the client id and secret).
  2. This site's building β€” choose the SE building the rooms are in. Discovery and Roll out then start with it. If SE shows the same point through two automation servers, list the right one in IoT settings β†’ Discovery.
  3. Rooms ↔ SE spaces β€” each room is matched to the space of the same name (Room 0101 is room 101); a space already linked to another room is not matched again, and a room that shares its space with another says Same SE space as room …. Link matched rooms links them all; Link links one. Any other room: choose its SE space in the SE space list of the Rooms table below (spaces grouped by floor; a space already linked to another room shows that room and cannot be chosen; Not linked unlinks it). Rooms that are not in SE simply stay unlinked. Changing the space of a room that has devices asks first β€” its devices stay; find them again in Discovery.
  4. Devices β€” Find devices on a room opens Discovery for it, with its space chosen: review the proposed lights, curtain, thermostat and courtesy panel and Apply. For many rooms of the same kind, save a tested room as a Room Template and Roll out the rest.
  5. Test and go live β€” run a Batch test in a room, then switch the site to Live in IoT settings β†’ Sites (Devices admin). Check the room is empty first.

Local β€” without a PMS, daily check-in and check-out

A hotel that keeps its reservations in the console (Reservations) can have guests checked in and out automatically every day, under Settings β†’ Integrations β†’ PMS β†’ Local:

Only an administrator changes the settings; the front desk sees the plan and can run it now.

New sites

A hotel signs up by itself: Start a free trial on the sign-in page, on the Provyl website (top right, and under Pricing), or /signup asks for the plan after the trial β€” Basic or Custom, monthly or yearly (the website's Pricing buttons choose it already) β€” your name, the hotel's name, a work email and a password. No card is asked for: the plan is only remembered, and Plan & billing shows it first (Chosen when you signed up) when you are ready to pay. Open the link in the email that follows β€” it opens Set up your property, where the site is created: a 14-day trial with up to 10 TVs, and you are its administrator in every area (invite your team in Staff). One person can have up to three sites on trial at a time; a signed-in person adds another site from the same page (/start). Someone signed in without any site β€” an account added by hand, or a site that was removed β€” is taken there too, instead of a No access screen; a person who should join their team's site waits for an invite instead.

Provyl staff can also create a site while installing its first TV: in Add TV, pick + New site… (this needs an admin grant for all hotels) β€” it starts on the trial too; set it to Not billed on Plan & billing for a pilot. A new site starts with the basic service package (Room devices off), a Standard template, and the default TV Preset.

Plan & billing

Settings β†’ Plan & billing (administrators) shows the site's plan, its status, the TVs installed and what the plan allows:

Plan What it allows
Trial 14 days, up to 10 TVs, the basic package. When it ends, the TVs keep working but no TV can be added.
Basic €1 per TV a month or €10 a year (at least 49 TVs β€” €49 / €490), any number of TVs, the basic package.
Custom Basic plus €500 a month (€6,000 a year, 12-month term): Room devices (IoT) and up to 8 hours of customisation a month.
Movies add-on Uploading movies (storage and watching are billed per 1,000 minutes) β€” added by Provyl.

Prices exclude VAT β€” see the website for the current prices.

AI credits

The AI β€” Ask AI, the setup guide, AI templates, translations, the operations assistant, Report a problem and the guests' AI concierge β€” uses credits by the AI tokens each answer needs. 1 credit = €0.01. Typical use: the whole setup guide about 2 credits, a question to Ask AI about 2, a new AI template about 40 (more with revisions), a guest's question to the concierge about 0.1.

Staff access

Settings β†’ Staff lists everyone who can open this site in the console. It is for administrators of the site (Admin area, role Admin).

Rooms & floors

Settings β†’ Property has three tabs: Rooms & floors and Room types β€” the rooms and their types β€” and Service package. Everything a room type gets is set where it is used (below).

Rooms lists every room of the site by floor, with its room type, how many TVs and IoT devices it has, and whether it is linked to the building management system. The IoT columns and the SE fields below appear once the site is connected to a building system (today Schneider Electric β€” Connecting Schneider Electric) β€” or when its rooms already have devices or SE references.

Guest language

Guest language on Rooms & floors chooses which of the apps' languages β€” English, Deutsch, FranΓ§ais, EspaΓ±ol, Italiano, Nederlands β€” guests are offered, and the default language. Tick the languages to offer (at least one), pick the default among them and press Save.

Room types

A room type (for example Deluxe or Suite) groups rooms. Here you set its name, description, amenities and photos β€” what a guest sees before check-in β€” and which rooms are of that type. Import from the PMS β€Ί opens the PMS connection, which can read the PMS's room types and rooms.

What a room type gets is set where it is used:

Photos (in Edit, once the type is saved): Add photos uploads JPEG, PNG or WebP images β€” up to 12 per type. Large photos are made smaller (1600 pixels on the long side) before they are uploaded, so phones load them quickly. The first photo is the cover, shown in the list and first in the guest's gallery; Cover makes another one the first, Remove deletes it. Photos are saved at once β€” they do not wait for Save. Guests see them, swiping through, on their app link before check-in. Deleting a room type deletes its photos too.

What a room gets is decided in this order (the same before, during and after a stay): the room's own template or preset (set in Content Manager β†’ Templates β†’ Features & rooms or TV Presets) β†’ the room type β†’ the site default. So set things once on the type, and give a single room its own template or preset only when it must differ.

Delete a type only when no room uses it β€” give those rooms another type first. With a PMS connected, its room types (Apaleo unit groups) are linked to these on the PMS connection card.

Building management at the bottom shows the site's time zone, SE device group, and whether the site's devices are Simulated or Live β€” see Simulated and live. Vendor passwords are never entered in the console.