A tour of Orkyo

Orkyo’s layout is a sidebar of main areas plus a top bar of cross-cutting tools. This page maps them; each area has its own documentation chapter for the details.

The main areas

The sidebar navigation lists the main areas, plus settings for those with the rights to see them. Resources sit under two entries, not one per type: what stands still, and what moves. Adding a resource type never grows this list.

Utilization — the home page and the scheduling board. A calendar and a timeline per resource; drag requests into place and review how resources are used over time. See The Utilization board.
Stations — “Resources with a fixed location, placeable on a floorplan”. Machines, cells and benches, plus the site plan they stand on. See Stations and The floorplan.
Assets — “Mobile resources, planned by availability”. People, tools and vehicles, including skills, absences and working availability. See Assets.
Requests — capture and organize the work that needs scheduling, as a tree or a list. See Working with requests.
Insights — conflicts and utilization analytics: KPI cards, trend charts over a period you choose, and the bottlenecks and critical path that constrain the plan. See Insights and KPIs.
Organization — “Departments, job titles and the rest of the organization’s shared reference data”. See Organization.
Settings (editors and admins) — shared definitions: criteria, templates, presets, and scheduling.
Configuration (workspace admins) — the kinds of resource this workspace schedules and the lists they carry: resource types, the type catalog, and list definitions. See Resource types.
Administration (workspace admins) — workspace governance: sites, users, organization, and integrations.

The top bar

Site selector — when your organization has several sites, Select site… scopes the boards to one of them.
Search (⌘K) — the global command palette. It indexes resources of every type — the machines, people and tools you activated and the types you defined yourself — plus requests, groups, sites, templates, and criteria. Each result is badged with what it is, and typing a resource type’s key (tool, car) brings up that whole class. Press Enter to open a result, Esc to close; results you have no rights to open are not listed.
Import / Export — context-aware: on a page with importable or exportable content, these buttons act on that page’s data (CSV/JSON, and a PDF export on the Utilization board). Included in the Professional and Enterprise plans on Cloud; always available in Community.
Messages — platform announcements; a badge counts unread messages.
User menu — Account, Switch Organization, Messages, Take a tour, About, theme toggle, and sign-out. Administrators also see Site Admin.

Sorting and filtering lists

Every list in Orkyo — stations, assets, requests, and each settings page — shares the same column headers. Click one to open a small menu: sort the column, or filter it with a control that fits the data — checkboxes with counts for statuses and types, a contains-box for text, a from/to range for dates and numbers. A filtered column shows a marker on its header, and Clear filter in the menu removes it.

The view you build lives in the page’s address, so a filtered list can be bookmarked, shared, or revisited with the Back button. On phones, lists render as cards without column headers; a filtered link still applies, but changing filters is a desktop/tablet affordance for now.

The guided tour

Take a tour (user menu) opens a step-by-step walkthrough that navigates to each real page as it explains it: Your resource types → Criteria → Templates → Stations → Assets → Organization → Requests → Conflicts → Utilization → Insights. It is the fastest way to see the setup path from Getting started in the product itself. A step you cannot reach is left out: the resource-types step needs the administrator role, and the two Settings steps need the editor role.

Roles decide what you see

What appears in the sidebar depends on your role: Viewers have read-only access to view utilization and plans; Editors can create and modify utilization, requests, and spaces but cannot access settings; Admins have full access to all features including user management and settings.