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.
12 capabilities
Benefit plans and enrolments are managed in the console, and employees see their own benefits in their account.
People and work · benefits
Team availability, a find-a-slot search and a personal day view read member calendars and workload for planning.
People and work · scheduling
Sprint planning, epics, backlogs and burndown and burnup charts sit on the project screens.
People and work · sprints
Surveys, their runs and responses, including an eNPS result, are managed on the people screens.
People and work · surveys
Tasks carry checklists, dependencies, blockers and recurring schedules and are worked from the projects screens.
People and work · tasks
Teams and their members are created and managed in organization settings.
People and work · teams
Attendance, attendance rules, leave, holidays, shifts and event crew muster are managed on the people and events screens.
People and work · time
Trips, travel segments, per diems and price caps are managed from the travel page of the console.
People and work · travel
Openings, applicants and applications are managed in the console, with interviews, scorecards, offers and talent pools served by the backend.
People and work · ats
A nightly reconcile builds task flow and project health facts that feed dashboards and metrics; the package serves no route of its own.
People and work · work-analytics
Timesheets are managed from the console; the time-log routes behind them were not traced to a screen of their own.
People and work · worklog
A March ticket and a June jar are two records today.
People and work · parties
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.