Appearance
Apps, rules and connectors
Making the platform do something — on its own, or in somebody else’s system.
Three different ways to act on what Omaya knows. Apps are self-contained products built on the platform — booking, roll call, washroom hygiene — which you switch on and staff then use directly. Rules watch a number and do something when it crosses a line. Connectors carry data in and out, to your own systems.
Nearly every page below is permission-gated. If a colleague cannot see one, that is their role rather than a fault — Roles is where to look.
Apps
Your apps
/admin/apps/your-apps
The apps enabled for your organisation, with their settings.
When you would open it. Configuring an app you already have — the booking calendar, roll-call rosters, cleaning schedules.
App Users
/admin/app-users
Accounts for the people who use an app rather than administer the platform — cleaners, receptionists, guards.
When you would open it. Giving a staff member access to their own app screens without giving them the admin console.
Before it has anything on it. An app enabled that has a staff-facing side.
Rules
/admin/manage/rule
Your rules: when this measurement crosses this line, do these things.
When you would open it. Turning a number into an action — an alert, an email, a webhook, a light switched off. There are templates for the common ones, and an AI builder that will draft a rule from a sentence.
Before it has anything on it. The metric you want must have a value for the scope you choose. Set a throttle, or a condition that stays true will fire every minute.
Connectors
/admin/connector
Everything that carries data in or out: gateways, MQTT, smart-home and Matter bridges, calendars, messaging channels, outbound webhooks, CMMS and storage.
When you would open it. Connecting Omaya to something else, and checking a connection that has gone quiet — each connector records its own last status and last error.
This list is read from the admin menu itself, so it cannot fall behind it.