Concepts
Temprix models team coverage from a handful of entities inside a workspace. This page names them in the order they depend on one another and links to where each is configured or explained in depth.
Workspace
Section titled “Workspace”A workspace is the tenant boundary for one organisation. It holds the member roster, teams, event configuration, billing, and data region. Nothing is shared between workspaces. Creation, dataset choice, and region are on Workspaces.
Member
Section titled “Member”A member is a person, or sometimes a non-person stand-in, inside one workspace. Members carry baseline availability, location for group-event matching, roles, and the events logged against them. The roster and access layers are on Members.
Members and users
Section titled “Members and users”A user is an account that signs in to Temprix. A member is a record in one workspace. They are not the same thing: a member does not need an email address and never has to become a user. When an email is present, it links to the matching user account and the person sees that workspace after sign-in. One user can hold members in several workspaces with no shared data between them.
A team is the group coverage is planned for. Timelines, outlook, alerts, and reports on a team use that team’s members, not the whole workspace. A member can belong to several teams, or to none. Teams are on Teams.
Event category
Section titled “Event category”Every event belongs to a category that sets scope (member or group), default availability, time type, colour, and stacking order. Categories are workspace-wide or team-specific. Detail is on Event categories and types.
Event type
Section titled “Event type”An event type is the selectable label within a category, such as Annual Leave or On-call Duty. It can override the category’s default availability and whether an event counts on non-working days. Types inherit from their category when a field is left empty.
Member event
Section titled “Member event”A member event is a whole-day claim about one person’s time: leave, training, on-call, and similar. It carries an availability value and an event type. Logging and overlap rules are on Member events.
Group event
Section titled “Group event”A group event applies to every member whose location matches, without naming individuals. Public holidays and office closures are typical examples. Matching uses country, subdivision, and locality. See Group events.
Baseline
Section titled “Baseline”Baseline availability is how much of a person’s time is ordinarily available
when no event covers the day. It is set per member, usually at 100%. A lower
baseline describes a permanent partial arrangement, not a day off. The working
week and baseline are on How availability works.
Availability
Section titled “Availability”Availability is the share of a member’s working day that remains available on a
given date, from 0% to 100%. It is resolved from baseline, the working
week, group events, and member events. Availability answers how much time
counts toward a team; it is independent of time type. The full model is on
How availability works.
Time type
Section titled “Time type”Time type classifies a period for reporting: Primary, Secondary, Standby, or Non-working. It is set on the event category and does not change availability or coverage. Reclassification affects time reports only. See Time type on Event categories and types.
Coverage
Section titled “Coverage”Coverage is a single number per team per day: the sum of each active member’s availability, expressed in people. Timelines, outlook, and alerts use it to show whether a team will be short. How that sum is produced is on How coverage is calculated.