Loading page
One catalogue for the whole platform, filtered to what applies to ojas.events. The page also publishes what the software does not do yet, in full and without burying it.
16 capabilities
Programmes with syllabi and modules, scheduled cohorts, and enrolments managed from the console.
Learning · academy
People keep an address book, and countries and pincodes are looked up through the backend.
Commerce · addresses
Organizers manage an event's attendees and scan people in, and ticket holders see their tickets in their account.
Events · attendees
An organization's administrators read a log of what happened in it, and a person reads their own activity.
Identity and access · audit
Benefit plans and enrolments are managed in the console, and employees see their own benefits in their account.
People and work · benefits
Bookable resources and bookings are managed in the console, with public places and dispatch routes served by the backend.
Places and assets · bookings
A shopper keeps a profile and preferences with a store and subscribes to back-in-stock and price alerts.
Commerce · customers
A customer sketches an occasion's budget as a plan with line items, kept apart from the organizer's internal job costing.
Events · event-plans
A customer buys a gift card in a set denomination, sees their wallet balance and history, and redeems it against an order.
Commerce · giftcards
Team availability, a find-a-slot search and a personal day view read member calendars and workload for planning.
People and work · scheduling
A signed-in person sees their active and past subscriptions on the My subscriptions page.
Commerce · subscriptions
Attendance, attendance rules, leave, holidays, shifts and event crew muster are managed on the people and events screens.
People and work · time
People can sign in with a password or one-time code, and list and end their own active sessions.
Identity and access · users
Billing configuration, invoices and commission schedules are managed in the console; subscriptions, usage and settlements are served by the backend without a screen traced for each.
Money and books · billing
The API lets a signed-in person set an appearance preference and change their email address by confirming a link; a hook exists for appearance, and no screen for either was found.
Identity and access · users
Live means a route, a screen and the data behind it are all reachable today. Live in part says what is and is not covered. Coming soon only appears with the work package that owns it, and any quarter shown is a target, not a promise. Not started carries no date.
Where a row replaces a limit we once published, it quotes that limit as we wrote it and dates the day the capability became reachable.