Tenant isolation.
Events live behind PostgreSQL row-level security. A tenant's calendar cannot leak into another tenant's query — the database enforces it, not convention.
How Weke Calendar keeps time honest
Scheduling you can audit.
A calendar coordinates sensitive work — onboarding, compliance, secure meetings. Weke Calendar treats every slot as a record: isolated per tenant, private by default, and logged when it changes.
-
01
Propose the slot
Slots come from real availability — free/busy computed server-side against the tenant's calendars and resources, never from a stale export.
-
02
Hold and confirm
Public bookings take a hold before they take a slot. A hold either confirms within its window or releases — a half-booked meeting cannot exist.
-
03
Remind and record
Confirmations schedule reminders and emit workflow events, so the rest of the platform reacts to the calendar instead of polling it.
- Complete trails
- Audit baseline
Private by default.
Visibility levels — normal, private, confidential — decide who sees what. Free/busy shares availability without sharing the meeting.
Automation on the record.
Rules and reminders act as the calendar, with their actions logged like anyone else's — automation never edits history in the dark.
Inside the calendar
The year, one glance deep
Twelve months of density at once — where the busy weeks cluster, and where the calm ones actually are.
