Why Majlis
Every large office has the same three problems: rooms booked and never used, no way to tell from the corridor whether a room is free, and no evidence when someone asks how space is really used. Majlis answers each one directly:
No more empty booked rooms
Every booking must be checked in — at the door, by QR sticker or in the app — or the room is released for others.
The door tells the truth
A tablet beside each room shows a colour readable from down the corridor, updated within two seconds — and says so honestly if it loses its connection.
Decisions on evidence
Every booking, check-in and no-show is recorded, so utilisation and no-show rates are a report, not a debate.
Built for organisations that must keep their data home: nothing leaves your data centre except the sign-in handshake with your identity provider. The name is the Arabic majlis (مجلس) — the room where people gather.
At a glance
One product, three surfaces, one server inside your own network — English and Arabic throughout, installed from an offline bundle.
Meeting rooms
Find a free room in three taps, and never lose it to a no-show.
| What you can do | How it works |
|---|---|
| Find a room | Filter by building, floor, time, seats and amenities. Only rooms free for the whole slot appear; if none, the nearest alternatives are offered. |
| See the schedule | Day or week view for any room; tap a free slot to book it. |
| Book | Title, attendees, private or not. Confirmed instantly, or sent for approval if the room needs it. Editable later. |
| Repeat | Daily, weekly on chosen days, or monthly, with an end date. Every occurrence and any clash is shown before you confirm; clashes are skipped, never silently booked. |
| Check in | At the door, by QR sticker or in the app, from ten minutes before the start. Miss the grace period and the room is released — you are told why. |
| Extend or end early | Extend from the door or the app, up to the next booking. End early and the room turns green at once. |
| Walk in | Take a free room on the spot from its door panel, for 15 to 60 minutes. |
| Private bookings | Shows only “Booked” to everyone else, including on the door. |
| Protocol rooms | Board rooms and senior offices: approval required, private by default, hidden from staff not on the access list, read-only door panel. |
A refused booking is explained in plain words in the user’s language — “Meeting Room 3 can be booked up to 14 days ahead” — never a code.
Door panels
A tablet beside every meeting-room door answers the corridor’s question — is this room free? — in one colour, readable from ten metres.
| Colour | The panel says | Meaning |
|---|---|---|
| Green | Available for 46 minutes | Free; walk in from the door |
| Blue (optional) | Available for 12 minutes | Free, but the next meeting is close |
| Orange | Waiting for check-in · auto-release in 6:40 | Booked; nobody has confirmed yet |
| Orange | Booking awaiting approval | A request holds this time |
| Red | In use until 11:00 | A meeting is running |
| Purple | In preparation | Set-up or clear-down time |
| Grey | Closed | Outside working hours, a holiday, or out of service |
Beside the colour: the room’s name in large type, capacity and amenities, today’s timeline, and the current meeting (or just “Booked” when it is private).
At the door, anyone can: walk in, check in, extend, end early, find another free room on the floor, report a fault in two taps, or scan the QR code to do the same from their phone.
What makes it trustworthy
- Two seconds. A check-in on a phone turns the door red within two seconds — updates are pushed, not polled.
- Honest when offline. Lose the network and the tablet keeps the last state, dims it and says Reconnecting… last update 09:41. It never guesses, and recovers on its own.
- The server is the clock. The time shown comes from the server; a tablet with a wrong clock cannot mislead anyone.
- No passwords on the tablet. A new tablet shows a six-character code; an administrator types it in and picks the room. One click revokes a lost tablet.
- Protocol rooms stay protected. Status only, no buttons — a senior official’s meeting cannot be ended from the corridor.
- Each panel in its own language, English or Arabic, set from the console.
Hardware: any current 10-inch Android tablet in a kiosk mount — no special device, no app store. Updating the server updates every panel.
Desks and floor plans
Upload a plan of each floor, place the desks on it, and staff book a seat by tapping it.
- Interactive floor plan. Every desk and room is a marker coloured by state — free, booked, yours, assigned, closed — with a glyph so colour is never the only clue. Pan and pinch on a phone; a list view for screen readers.
- Hot desks and assigned desks. Hot desks are bookable by anyone for a day or part of one. Assigned desks belong to a named person, who can release theirs for a day away.
- Check in with a sticker. Scan the desk’s QR code and the booking is confirmed; unclaimed desks are released after the grace period.
- Who’s here. Show who sits where today — or just “Booked”, if you prefer; administrators always see names.
- Printable labels. A sheet of QR labels per floor, each space named in both languages.
The editor is drag-and-drop; replace the plan image and every marker keeps its place.
Rules and approvals
Your rules, applied the same way every time — by the system, not by whoever is on duty.
A booking policy is a named set of rules for a group of rooms or desks:
| Rule | Example |
|---|---|
| How far ahead | 14 days for meeting rooms, 30 for the board room |
| Shortest and longest booking | 15 minutes to 4 hours |
| Working hours per weekday | Sunday–Thursday 07:30–14:30; closed Friday and Saturday |
| Holidays | Site-wide dates close every space; affected organisers are told |
| Check-in window and grace | Opens 10 minutes before the start; released 10 minutes after if unclaimed |
| Preparation time | 15 minutes blocked before and after each board-room meeting for set-up |
| Bookings per person | At most five upcoming per person |
| Who may book | By role, or a named access list per room |
| Approval | On or off per policy |
| Door panel | Full actions, or read-only for protocol rooms |
| Visibility | Open to all, or hidden from staff not on the access list |
Three ship by default — Meeting rooms, Protocol rooms and Desks — editable at any time. Changes apply to new bookings only.
Approvals. A request holds the time so nobody else can take it. Approvers see a queue — who, which room, when, how many — and approve or reject with a reason; the requester is told at once. Undecided requests lapse when the meeting is due. Approvers can be scoped to buildings or rooms.
Notifications. In-app alerts for every decision, release and cancellation; email through your own mail relay. Nothing goes through third-party services.
Administration console and reports
One console, in your language, for everything facilities and IT need — and the numbers to run the building on evidence.
Manage
- Buildings, floors, rooms and desks with names in both languages, capacities, amenities and access lists; closing a space cancels its bookings with notice to each organiser.
- Floor-plan editor — upload, place, drag; print QR labels per floor.
- Policies — every rule above, in a form; holidays by date.
- People — roles (staff, approver, administrator), deactivation, bookings on someone’s behalf.
- Door panels — pair with a code, see which are online, unpair in one click.
- Issues reported from panels, with resolution notes.
Reports
Any date range, by building and floor; CSV exports that open correctly in Excel with Arabic text.
| Report | Answers |
|---|---|
| Utilisation by room or desk | Hours actually used as a share of opening hours — which rooms earn their space |
| Bookings by weekday and hour | A heat map of demand — when the building is full |
| No-shows by room | Booked but never checked in — where to shorten the grace period |
| Desk occupancy by floor | Average and peak seats taken |
| Top organisers and most-booked spaces | Who and what drive demand |
Audit log. Every booking and administrative change — who (a person, a panel or the system), what, before and after, when — searchable, exportable and append-only: not even an administrator can edit or delete it.
Arabic first, accessible to everyone
Arabic in Majlis is a first-class language, not a translation layer bolted on afterwards.
- A real right-to-left layout. Switch to Arabic and everything mirrors — navigation, tables, forms, timelines, the floor plan and the door panel. Only images and QR codes keep their orientation.
- Your choice of numerals, Western (0–9) or Arabic-Indic (٠–٩), applied everywhere; Arabic plural forms done properly (مكتبان متاحان, ٣ مكاتب متاحة).
- Two names for everything. Buildings, floors, rooms, desks, amenities and policies carry both names; each person, and each panel, sees its own language.
- Modern Standard Arabic as used in official correspondence, reviewed with a native speaker; every string lives in one file, so wording can be refined without touching the software.
Accessible by design (WCAG 2.1 AA): colour is never the only carrier of meaning; 4.5:1 text contrast; full keyboard operation; large touch targets; list and table alternatives to the floor plan and every chart; door-panel type readable from three metres.
Security and privacy
The design starts from one promise: your data never leaves your building, and every change is accountable.
The data stays home
- Every record — people, bookings, floor plans, backups, logs — lives on servers you control. No vendor cloud, no telemetry, no analytics, no external fonts or scripts; the browser is told by policy to load nothing from anywhere else.
- The only outbound connection is the sign-in handshake with your identity provider, which learns that someone signed in — nothing about rooms or bookings. Sites that permit no outbound connection run in local-accounts mode.
- Support runs through your IT staff, on-site or by screen-share with your administrator at the keyboard. The supplier has no remote access and receives no data.
Identity and access
- Staff sign in with their existing accounts (Google Workspace or Microsoft Entra ID) over OpenID Connect, restricted to your domain or tenant; personal accounts are refused.
- Three roles — staff, approver, administrator — assigned by you. Every permission is enforced on the server.
- Sessions expire after 12 hours idle, 7 days at most; deactivating a person ends their sessions and cancels their future bookings.
- A separate local administrator account exists for installation and emergencies, kept off the general network.
Least privilege everywhere
- A door panel’s token works for one room only; it cannot list people, other rooms or private meeting titles. One click revokes it.
- Private bookings show “Booked” to all but the organiser and administrators — on the door, in the app, in the schedule.
- The application’s database role cannot alter or delete the audit log, and cannot change the schema.
Accountability
- Every change is recorded — who (a person, a panel or the system), what, before and after, when — append-only, exportable, and forwardable to your SIEM.
- Double-booking is prevented by the database itself, not by application code that could race under load.
Hardened and assured
- HTTPS only with your certificate; strict Content Security Policy; secure, HttpOnly, same-site cookies; passwords hashed with scrypt; panel tokens stored only as hashes.
- Uploads are type-checked and sanitised; exports are protected against formula injection; every input is validated.
- Pinned dependencies and a software bill of materials per release; an independent penetration test before go-live, report handed to you; critical fixes within 7 days.
- Nightly backups on your encrypted storage, a rehearsed restore, 12-month log retention — all inside your perimeter.
Privacy by design
Majlis stores the minimum: a name, a work email, a department and booking records. No location tracking, no camera access, no behavioural analytics. Data is kept as long as your retention policy says, and exportable in open formats at any time.
Deployment and operations
One virtual machine, one bundle, about ten minutes to install — and your IT team can run it without us.
| Server | One Linux virtual machine (4 vCPU, 8 GB, 100 GB) running four containers: application, PostgreSQL, TLS proxy, backups. Sized for 3,000 users, 300 rooms, 3,000 desks and 150 panels. |
| Install | One offline bundle: verify the checksum, run install.sh, answer a few questions. No internet needed on the server at any point. |
| Updates | Load the next bundle and restart — under 15 minutes, with an automatic pre-update backup and a rollback path. |
| Backups | Nightly, kept 14 days on your storage, restore rehearsed. Recovery point 24 hours, recovery time under 4 hours; disaster recovery to a second machine in about 30 minutes. |
| Monitoring | A health endpoint for your monitoring tools: application, database, scheduler, last backup, offline panels. Logs kept 12 months; security events to your SIEM. |
| Certificates | Your own TLS certificate, public or internal CA; renewal is a file copy and a restart. |
| Panels | Any current Android tablet in a kiosk browser; ten-minute setup per tablet with a checklist. |
| Support | From inside the country, through your IT staff; a named contact, response times by severity, no remote access to your data. |
Getting started
From agreement to go-live in about five weeks, with something demonstrable at the end of every week.
Installed together with your IT team, on a server in your own data centre, with your floor plans and your booking rules.
What you receive
- The system installed, configured and accepted against written scenarios
- The complete source code, the offline install bundle and every update
- Administrator manual, operations runbooks, a one-page staff guide in both languages, recorded training
- An independent penetration test report and a software bill of materials
- A 12-month warranty and in-country support with response times by severity
See it in motion
Three short walkthroughs: the staff app, a door panel, and the console.