Prism Tenant Bookings in Door Tablet In this video, we will Demonstrate how tenants reserve common areas using Door Tablet displays connected to Building Engines Prism Show how Prism permissions control who can and cannot reserve rooms Explain how employee IDs are validated to ensure secure, accountable bookings Walk through the configuration steps required in both Prism and Door Tablet Admin Door Tablet offers several reservation options when working with Prism In this video, we will focus on using Door Tablet room displays to create tenant reservations, validating employee IDs during booking and enforcing Prism-based permissions to control who can reserve rooms First, we begin on a Door Tablet display that is already connected to your Building Engines Prism environment We will now log in to the Door Tablet server and select the room we will use for our test, for example Room 101 The first thing that happens is that Door Tablet binds to the Prism account and fetches the schedule for this room and we can see that there are currently no meetings booked for this room We can start the booking process by tapping the crosshair icon in the corner of the screen From the menu that appears we tap “Reserve” to begin creating a new room reservation We are first asked for an email address so we type the email address of the person who wants to reserve the room In this first example, we see what happens when the user record in Prism does not have an employee ID Door Tablet rejects the booking because, in our configuration on this system users must have an employee ID and blank IDs are not accepted To demonstrate a different scenario we now try a second email address that does exist in Prism but still does not fully meet our reservation rules We enter the new email address, wait for the lookup to complete and watch as Prism successfully identifies the person and Door Tablet then prompts us for an employee ID If the user does not remember their employee ID we can tap the on-screen link to ask the system to send an email to that user with their employee ID details For the purposes of this demonstration, we assume we know the employee ID and type it directly into the field We then set the desired duration for the meeting for example, choosing a one-hour booking and adjust any attendee information as needed Next, we tap “Reserve” and observe what happens when the user has an employee ID but is not authorized to book rooms In this case, Door Tablet sends the reservation request to Prism but Prism rejects it because the user’s permissions do not allow them to reserve meeting rooms for this property Now we will try again and enter the email address of a user who exists in Prism has an employee ID, is assigned to the correct permission group and is associated with the building that contains Room 101 We watch as the reservation is confirmed, with the Door Tablet display showing the room as busy, and we can see that Prism has created the reservation and sent any relevant confirmation messages Let’s see what we had to do to make this work In the Prism web interface, we configured permissions First, we navigate to “Manage Permissions” in Prism where we control which users can create room reservations We select the appropriate permissions group that we want to allow to create reservations for example a tenant admin group Within that group, we open the resource reservation section Here, we enable the option “Can create reservations” which gives members of this group the right to book meeting rooms After enabling this permission, we make sure this group is assigned to the correct users without this assignment, users will still be unable to reserve rooms Next, we go to the Users area in Prism to review individual user records We locate the user who was able to reserve rooms, for example the sales user and open their profile We confirm that this user belongs to the Tenant Admin group If you do not want people to be able to reserve, you do the reverse In that group’s resource reservation tab we verify that all reservation-related options are disabled ensuring that members of that group cannot make bookings Now we switch to the Door Tablet Admin interface to configure how employee IDs and Prism are used together Just to note, employee IDs do not have to be unique and that a single employee ID could be used for a group of users if needed although using a variety of IDs is recommended to reduce the potential for abuse Next, we log into the Door Tablet Admin web UI to see the configuration required from there Let’s open the Integrations section We scroll down until we reach the user ID source settings Here, we select Building Engines Prism as the source of user IDs so that Door Tablet relies on Prism for identity and verification Here is where we enable the option that requires an employee ID for making reservations, ensuring that unidentified users cannot book rooms If we tick this box, we can allow blank employee IDs but in this demonstration we keep a strict setup and do not allow blank IDs Finally, we submit or save these configuration changes so they take effect for all future reservation attempts To summarise, we have seen how a missing employee ID prevents bookings how incorrect permissions in Prism block reservations and how proper configuration in both Prism and Door Tablet Admin allows tenants to reserve rooms safely and accountably using Door Tablet Thank you for watching Door Tablet provides room scheduling and meeting room management for modern workplaces.