How a panel gets its settings
A panel holds almost nothing of its own. Its buttons, its identification and its look come from a named configuration that other panels share — which is why changing one panel can change twenty.
Nothing you change about a panel is stored on the panel. Its buttons, the credentials it asks for, its skin and its screen saver all come from a panel configuration — a named set of settings that any number of panels point at.
That is the one thing to understand before anything else in this section, because it is what makes “I changed one panel and it changed the whole floor” an accurate description of what happened rather than a bug.
Open Panel configurations
One configuration, with Linked to naming every panel that follows it.
Every setting sits on one of its pages
Opening a configuration opens a rail of pages, and knowing which page holds what saves most of the hunting:
- Basic — name, languages, clock format.
- Design — skin, logo, background, text sizes.
- Function — which buttons the panel offers: Show walk in button, Show check-in button, Show check out button, Show extend button.
- Check-in method — what the panel accepts as proof of who somebody is, and whether it may accept nothing at all.
- Screen saver, Color control, Monitoring, Other.
The rail. Function and Check-in method are the two pages the rest of this section keeps sending you to.
Making one panel behave differently
There is no per-panel override. A panel that has to behave differently needs a second configuration, and then to be moved onto it.
Both halves are done from the same dialog: build the configuration, then open Booking panels, under Assigned device at the foot of the rail, and tick the panels it applies to. The same move can be made from the other direction, on the panel list, by setting a panel’s configuration there.
Every panel in the estate, by building and floor, with this configuration's ticked.
A lobby panel that should not let passers-by take the room, and a team-floor panel that should, are two configurations. So are a panel with a card reader and one without.
What this does not control
- Who may book the room, and for how long. That is the resource’s policy — see Resource policy settings.
- Whether check-in is required, and how long somebody has to do it. Also the policy — see How check-in and no-show work.
- Which credentials exist at all. The organisation-wide Check-in method screen sets the default for every panel; a configuration may override it, and that is the subject of How somebody proves who they are at the panel.
- Which room a panel shows. That is the panel’s own resource assignment, not a configuration setting.