Rooms and equipment
Managers define rooms/equipment needed by services; reservations prevent conflicts.
Managers define rooms/equipment needed by services; reservations prevent conflicts.
Where to find it
Web: open Bookings. Desktop: Business → Bookings, using the same record paths. Disabled modules or missing read permission remove the navigation entry.
| Screen / tab | Web path | Usage | Desktop |
|---|---|---|---|
| Resources | /resources | List, view or tab | Native screen |
| Record details | /resources/[id] | Record or editor | Native screen |
Start working
Step 1
Add a resource and availability.
Step 2
Associate services.
Step 3
Create one-off/weekly reservations.
Step 4
Cancel reservations or archive the resource.
Settings
Option-by-option configuration and screen paths: Settings guide.
There is no separate settings route; the guide distinguishes record options from declared defaults.
Permissions and limits
Before you start
Resource reservations are not customer appointments. Configuration is on the record, without separate settings.
Role capabilities: Read (read), Write (write), Manage (manage), Export (export), Comment (comment).
Own-record restrictions apply equally to lists, records and Era. Record state or missing data can refuse an otherwise permitted action.
Ask Era
Is a room free tomorrow at 14:00?
Select relevant records for Era context. Era respects modules/roles; external or confirmation-sensitive work can stop for approval. Use era tools in the terminal to inspect currently available tools.
Automation and events
These declared events are available to module-event triggers. Subscribing does not configure the next operation; choose recipients, conditions and actions separately.
Operation details
The inventory includes record, configuration, visitor and background flows. IDs support Era/automation; not every row is a menu button. Asterisks mark required inputs. Unmapped rows do not imply a visible control.
| Operation and ID | Inputs | Permission | Screen or flow |
|---|---|---|---|
Add a resource · resources.create | — | Manage | /resources |
Edit a resource · resources.update | Resource *, Name, Kind, Bookings at once (1–1000), Opens, Closes, Booked per (minutes; 1440 = by the day) (5–1440), Colour, Description | Manage | /resources |
Archive · resources.archive | Resource * | Manage | /resources/[id] |
Set the services that need it · resources.set_services | Resource *, Services | Manage | /resources/[id] |
Book a resource · resources.book | Resource *, From (local, YYYY-MM-DDTHH:mm) *, Until (local, YYYY-MM-DDTHH:mm) *, Customer, Appointment (the staff half), Note | Write | /appointments/new, /resources |
Hold every week · resources.book_weekly | Resource *, Subscription *, First week from (local) *, First week until (local) *, Note | Write | /resources |
Cancel booking · resources.cancel_booking | Booking *, Reason, Every week still to come | Write | /resources/[id] |
Related guides
Settings
Options, screen paths and defaults.
Workflows
Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.
Bookings
Bookings — modules and detailed settings
Technical sources
packages/os-kernel/src/modules/resources.ts, packages/os-kernel/src/modules/index.ts, apps/studio/lib/os/navigation.ts, apps/studio/lib/os/settings-groups.ts, apps/era-station/apps/web/src/era/business/screens.ts.