Events
Event teams manage dated venues/capacity, registrations and attendance.
Event teams manage dated venues/capacity, registrations and attendance.
Settings
Options, screen paths and defaults.
Browse this area
Marketing — modules and detailed settings
Where to find it
Web: open Marketing. Desktop: Business → Marketing, using the same record paths. Disabled modules or missing read permission remove the navigation entry.
| Screen / tab | Web path | Usage | Desktop |
|---|---|---|---|
| Events | /events | List, view or tab | Native screen |
| Record details | /events/[id] | Record or editor | Native screen |
Start working
Step 1
Create an event.
Step 2
Review registrations.
Step 3
Register/cancel and mark attendance.
Step 4
Change event status.
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
Events are separate from class series. Capacity/publication are on the event record, without separate settings.
Role capabilities: Read (read), Write (write), Export (export).
Own-record restrictions apply equally to lists, records and Era. Record state or missing data can refuse an otherwise permitted action.
Ask Era
Show next month’s events with capacity and registration counts.
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 |
|---|---|---|---|
Create an event · happenings.create | — | Write | /events |
Edit an event · happenings.update | Event *, Title, Description, Where, Starts, Ends, Places (1–100000) | Write | /events |
Open registration · happenings.publish | Event * | Write | /events/[id] |
Cancel the event · happenings.cancel | Event *, Reason | Write | /events/[id] |
Close the door list · happenings.complete | Event * | Write | /events/[id] |
Save a ticket · happenings.save_ticket | Ticket, Event, Name, Catalog item, Price (minor units), Currency, Places for this ticket | Write | /events/[id] |
Remove a ticket · happenings.remove_ticket | Ticket * | Write | /events/[id] |
Register a person · happenings.register | Event *, Ticket *, Person *, Places (1–50), Note | Write | /events/[id] |
Check in · happenings.check_in | Registration, Event, Door code | Write | /events/[id] |
Cancel a registration · happenings.cancel_registration | Registration *, Reason | Write | /events/[id] |
Register online · happenings.register_online | Event *, Ticket *, Places (1–10) | Write | Record/API/visitor flow; no separate screen button mapped |
Related guides
Settings
Options, screen paths and defaults.
Workflows
Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.
Marketing
Marketing — modules and detailed settings
Technical sources
packages/os-kernel/src/modules/happenings.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.