Core concepts

Temprix organizes scheduling data around a few core entities. This page is a glossary with links to detailed guides — not a manual.

Workspace

The top-level container for all data in Temprix. Each workspace has its own members, teams, event configuration, and reports. Users can belong to multiple workspaces and switch between them.

→ Workspaces

Member

A person tracked in a workspace. Members appear on the timeline and in capacity calculations. A member is not the same as a user account — one user can be a member in several workspaces.

→ Members & roles

Team

A group of members within a workspace. Teams scope timeline filters, reports, and can override workspace-level event categories and types.

→ Teams

Event category

A grouping for event types that shares a default capacity modifier, color, and scope (member vs. group). Categories define how events affect availability at a high level.

→ Event categories & types

Event type

A concrete unit for scheduling — Training, Vacation, On-call, and so on. Each type belongs to a category, has an icon, a default modifier, and a scope (member event or group event).

→ Event categories & types

Member event

A schedule entry for one member on one or more dates. Member events reduce (or restore) that member’s daily capacity according to the event’s modifier.

→ Creating & managing events

Group event

An admin-only event that applies to multiple members at once — typically holidays or company-wide closures. Group events use the group-event scope and can target by geography or cohort.

→ Group events & holidays

Capacity

The derived availability of a member on a given day, expressed as a fraction from 0.0 (fully unavailable) to 1.0 (fully available). Capacity is calculated from overlapping events using the minimum modifier rule.

→ How capacity works

Entity relationships