Three apps built into your LumApps intranet let your employees book desks, lockers, parking spaces or rooms managed in Comeen, and let your facility managers run those resources. This guide explains how to install, set up and use them.
The three apps
The apps read and write directly in your Comeen space: a booking made in LumApps shows up in Comeen straight away, and the other way round. They are displayed in English, French or Spanish depending on each user's language.
App | For | What it does |
Book a resource (WEX - Book a Resource) | All employees | See today's bookings, find a free resource for a date and time slot, and book it in a few clicks |
Manage resources (WEX - Manage Resources) | Facility managers | Create and edit resource types and their opening hours; add, edit, assign or delete resources |
Bookings overview (WEX - Bookings Overview) | Managers | See every booking for a day or a week, by type, with filters by building, person or resource |
Install the apps and the Comeen connector
Allow about 30 minutes, with a LumApps administrator account and a Comeen administrator.
Before you start
Your Comeen space ID (UUID).
Access to the Comeen API (OAuth 2.0): a Client ID and a Client secret provided by LumApps, with the
bookable_resources:read,bookable_resources:writeandusers:readpermissions.Comeen accounts whose email address is the same as the employees' address in LumApps: this is how the app knows who is booking.
If you don't have your Comeen space UUID or your Comeen API access (Client ID and Client secret), ask your LumApps contact.
1. Create the Comeen connector
The connector lets the apps call the Comeen API. Create it first: you will select it when you enable each app.
In LumApps, click the gear icon, then Settings, and open connector management.
Click New connector.
Information: enter a name, for example "Comeen".
Provider: type Comeen, Base URL
https://api.comeen.io.Protocol: OAuth 2.0, with the Client credentials grant type (application access, recommended).
Settings: enter the Client ID and Client secret, the Token URL
https://api.comeen.io/oauth/token, and thebookable_resources:read,bookable_resources:writeandusers:readscopes.Click Save.
2. Install and enable the three apps
In Settings, open Extensions → Extensions library.
On the WEX - Book a Resource card, click Install. Do the same for WEX - Manage Resources and WEX - Bookings Overview.
Open Extensions → Installed extensions: the three apps are listed, installed but not yet active.
For each one, click the edit button and open the Settings tab: select the Comeen connector created in step 1, turn on the switch that makes the extension available, then click Save.
3. Add the style
For the WEX look (cards, icon badges, primary colour), paste the wex_microapps.min.css file provided with this guide into the site's custom CSS, after the existing CSS. Otherwise, paste the wex_microapps_widget.html file into an HTML widget on the page. Without this CSS, the apps work with the default LumApps style.
Add the apps to a LumApps page
Once enabled, the apps are placed on your LumApps pages, each in a Display a micro-app widget. The same app can appear on several pages, with different settings.
Add an app to a page
Open the page in edit mode (gear icon → Edit), or create a new page.
Add a Display a micro-app widget in a single-column row: the apps are designed for full width, and the WEX style widens that row on desktop.
In the widget, select the app: WEX - Book a Resource, WEX - Manage Resources or WEX - Bookings Overview.
If the widget shows a Connector list, check that the Comeen connector is selected.
Fill in the widget settings: at least Comeen space UUID, and if needed the colour, time zone, type or building (see "Customise the widget" below).
Repeat for each app you want on the page.
For the managers' page, restrict access to their group in the page settings (see "Who sees what").
Click Save and publish.
Customise the widget
The settings are in the widget panel, in the page's edit mode. Only Comeen space UUID is required; the others have a default value and can be changed at any time, followed by Save and publish.
Setting | Apps | Effect |
Comeen space UUID | All three | ID of your Comeen space (required) |
Primary colour | All three | Colour of buttons and highlights, as a hex code (e.g. #1F6FEB). Empty = Comeen purple. Button text switches to white or dark depending on how light the colour is |
Language | All three | auto = each user's language; fr, en or es to force a language (for example on a kiosk) |
Time zone | All three | Time zone of the site (e.g. Europe/Paris, Europe/London) |
Resource type (id) | Book | Locks the app to a single type, for example for a "Parking" page; empty = the user chooses |
Building (id) | Book | Only offers the resources of one building |
Default resource type (id) | Overview | Type shown in the first tab |
Default building (id) | Overview | Building selected when the app opens |
Examples: a "Parking" page with Resource type set to the ID of the Parking type; one page per site with that site's Building and Time zone; a self-service kiosk with a forced Language. A type's ID is shown in Manage resources, under its name.
Check
With an employee account, open the Book page: today's bookings are shown, and a test booking appears in Comeen.
With a manager account, check that Manage resources lists your types with their ID.
Check that an employee account cannot open the managers' page.
Who sees what
Access to the LumApps pages and the permissions of the Comeen access decide what each person can do. We recommend this setup:
Book a resource: visible to everyone. Each person books in their own name.
Manage resources: managers only. Among other things, it can delete a resource together with all its bookings, with no way back.
Bookings overview: managers only. It shows the names of the people who booked and lets you search them by email; let your DPO know if needed.
A resource assigned to a person (for example a named desk or locker) can only be booked by that person.
Set up your resource types
A type groups similar resources ("Lockers", "Parking", "3rd floor desks"). Its settings decide what your employees choose when they book. In Manage resources, click ＋ New type, or Edit next to an existing type.
Booked by
Option | What the employee sees |
Day | They choose a date; the resource is booked for the whole opening day |
Half day | They choose All day, Morning or Afternoon (split at 1 pm) |
Hour | They choose a start and end time, in one-hour steps |
Quarter hour | They choose a start and end time, in 15-minute steps |
Booking hours
Choose "Limit to the hours below", then a time range for each day; "Closed" closes the day. The hours are shown under the type choice, and a closed day suggests the next open day. Without a limit, bookings are possible from 8 am to 7 pm.
A few details:
the hours are saved at the end of the type's description in Comeen, as
[[hours:{...}]]: do not edit this block by hand in Comeen;they apply to bookings made from LumApps, not to bookings made in the Comeen apps;
untick "Employees can book this type" to hide it from the booking app.
Type ID
Under each type's name, Manage resources shows its ID (for example "12 resources · ID 42"). This is the value to enter to lock a widget to a type (see "Add the apps to a LumApps page").
Using the apps day to day
Book a resource (employees)
The home screen shows today's date and your bookings for today.
In "Book a space", choose the booking type and the date, then click Show availability.
Choose your time slot: All day, Morning or Afternoon, or a start and end time depending on the type. Opening hours and slots that are already over are taken into account.
The list of free resources is shown; the last resource you booked is suggested first. Click Select.
The "You're booked!" screen confirms the booking, which you will also find in Comeen.
To cancel a booking, use Comeen: cancelling is not available in LumApps.
Manage resources (managers)
Add a resource: click Manage next to the type, then ＋ Add a resource. Enter the name, the location, and whether employees can book it.
Assign a resource: in the resource form, enter the person's email in "Assigned to". Only that person will be able to book it.
Edit or delete: click Edit next to the resource. Deleting asks for confirmation and also removes all the resource's bookings.
The list shows, for each resource, whether it can be booked and whether it is booked today.
Bookings overview (managers)
The screen opens on today's bookings, with one tab per type and the occupancy ("8 of 24 resources booked").
Click ⚙ Filter to choose a building, a date, a period (day or week) or search for a person or a resource, then click Show.
Frequently asked questions
What you see | What to do |
"Nothing available" | Try another time slot or another date |
"… is not available on …" | The type is closed that day: the app suggests the next open day |
"This resource has just been booked for this time slot" | Someone booked just before you: choose another resource |
My bookings for today are not shown | Check that your Comeen account uses the same email address as LumApps |
"No Comeen account matches …" (Manage) | The person you want to assign the resource to has no Comeen account with that email |
"No bookable resource type is set up in this space" | Create a type in Manage resources and tick "Employees can book this type" |
Message about the Comeen connector not being authorised, or about missing permissions | Check the Comeen connector (Client ID, Client secret, scopes) and that it is selected in the widget; if needed, ask your LumApps contact to add the missing permissions |
"Micro-app not configured" | Fill in the widget's Comeen space UUID setting |
The colour does not change | Check the code entered in Primary colour (6 characters after the #, e.g. #1F6FEB) |
For any other question, contact your LumApps representative.