Event categories & types
Event categories and types define what your team can log on the timeline. A category is the grouping; a type is the concrete unit members select when creating an event.
Categories
Section titled “Categories”A category groups related event types and shares:
- Default capacity modifier — the baseline availability impact (e.g., Time Off → 0.0, Training → 0.5)
- Color — used on the timeline and in reports
- Scope — member events, group events, or both
Categories exist at the workspace level. Teams can override with team-scoped categories.
Event types
Section titled “Event types”An event type belongs to exactly one category and adds:
- Name and icon — what members see in the event picker (e.g., “Vacation”, “Training”)
- Default modifier — can override the category default for this specific type
- Scope — member event or group event
When a member creates an event, they pick a type. The type’s modifier applies unless overridden at the event level.
Member vs. group scope
Section titled “Member vs. group scope”| Scope | Who creates | Example |
|---|---|---|
| Member event | Any member (for self or teammates) | Vacation, training, on-call |
| Group event | Admins only | Public holidays, company closure |
Group-scoped types appear only in the admin group-event flow. Member-scoped types appear in the member event picker.
Default dataset reference
Section titled “Default dataset reference”The Default dataset includes these categories and types:
| Category | Modifier | Example types |
|---|---|---|
| Time Off | 0.0 | Vacation, Sick leave, Unplanned TO, Planned TO |
| Holidays | 0.0 | Public holiday |
| Training | 0.5 | Training, Conference |
| Offsite | 0.3 | Offsite, Travel |
| Ops | 0.5 | On-call, Incident response |
| Other | 1.0 | Working from home, Other |
Skip custom configuration if the defaults fit your workflow. You can add types later without disrupting existing events.
When to create custom types
Section titled “When to create custom types”Create a custom category or type when:
- The default modifier doesn’t match your team’s reality (e.g., on-call at 0.7 instead of 0.5)
- You need a distinct color or icon for reporting clarity
- A team needs types that other teams shouldn’t see (use team-scoped configuration)
Reuse existing categories when the modifier and color already fit. Avoid duplicating types that differ only in name.
What to read next
Section titled “What to read next”- Modifiers & precedence — how modifiers resolve when events overlap
- Creating & managing events — what members see when logging events
- Group events & holidays — admin-only group-scoped events