Events & participants

The event, the people, the materials

An event isn't just a block of time — it carries the people invited, their answers, and links to the actual content the meeting is about.

The event

A block of time, fully described

Every event belongs to a calendar and carries the fields a scheduler actually needs — no more, no less.

A required title, an optional description and free-text location.
Timezone-aware start and end timestamps — an event can never end before it starts; the database enforces it.
An all-day flag for date-scoped entries alongside timed ones.
Set it to repeat and the event becomes a series — see Recurrence.

event

TitleQ3 planning

WhenTue 14:00 – 15:30

LocationRiverside room

All dayoff

RepeatsWeekly on Tuesday

Participants

A participant binds a profile to an event — one row per person, with their role and their current answer.

Each participant carries a role — attendee by default — and an RSVP status: accepted, declined, or still pending.
Participants are platform profiles, so the invite list is searched from the people you already have.
Adding is an upsert and removing is explicit — the event editor diffs your working list and applies exactly the changes you made.
Status lives on the participant record, so a response is data you can query — not a flag lost in an inbox.

participants · 3

Amara Oseiorganizeraccepted

Jonah Reyesattendeeaccepted

Mei Linattendeepending

Attachments

Attachments aren't uploads bolted onto an event — they're links to content that already lives in the platform.

An attachment points at a document or a collection — one target per link.
Each link carries a relationship label — attachment by default, or something more precise like agenda or minutes.
Because the target is real platform content, it keeps its own permissions, versions, and life after the meeting ends.

attachments

agenda Q3 planning agenda

minutes Q3 planning notes

materials Q3 research collection

Keep exploring