Skip to content

Quickstart

This page is the hands-on path from account to a first coverage figure. Entity names and how they connect are on Concepts.


Before creating an organisation workspace, Temprix offers a demo workspace seeded for exploration. After sign-in, open Create workspace and choose Demo as the initial state (the form pre-selects it when opened from the link).

The demo dataset loads a fictional organisation with about 30 members across Support and Engineering teams, member and group events, public holidays, and populated coverage reports. Nothing in a demo workspace affects a real organisation.

Work through the in-app getting-started guide inside the demo to open timelines, reports, and settings with data already in place.


When the organisation is ready for its own data, create a workspace from Create workspace after sign-in.

Creation requires a name, a data region, and an initial state (dataset):

Initial state What is seeded
Default Global event categories and types only; a team named like the workspace with the creator as its only member
Demo The default catalog plus members, teams, events, and holidays (see above)

Temprix also assigns a namespace (the URL segment for the workspace). It is derived from the name and is not chosen during creation. Names can change later; the dataset and region cannot.

Each workspace is created in United States (use1) or European Union (euc1). Data is stored and processed in that region.

Full detail on datasets, namespace rules, and settings is on Workspaces.


After a Default workspace is created, Temprix opens an in-app getting-started guide. The steps below are the same work in broader terms.

The workspace roster holds everyone who can appear on timelines and enter coverage. Adding someone requires a display name; an email address is optional but links the record to a user account when they sign in with that address.

Free workspaces allow 10 active members. Adding an eleventh creates the member as restricted: they can sign in and read, but do not enter coverage until a seat frees up or the workspace upgrades. See The Free member cap.

Demo workspaces skip this step.

A team is the group coverage is planned for. A Default workspace starts with one team (named like the workspace) containing only the creator. Additional teams group members for separate coverage targets. Creating a team does not add members; assign membership separately.

The Demo dataset seeds an all-company team and smaller functional teams.

On the Default dataset, Temprix seeds a global catalog of event categories and types (leave, operations, holidays, and similar). Review what is in place under workspace settings and adjust names, availability defaults, or enablement to match how the organisation works. This step can be deferred; the seeded catalog is usable immediately. Detail is on Event categories and types.

Group events apply to every member whose location matches, without naming individuals. Public holidays and office closures are typical uses. Add them once per country or location so coverage reflects non-working days across the roster.


Coverage Outlook plots forward coverage against a target for a team. Open a team, then Reports, and use the Coverage outlook tab.

In a demo workspace, pick a seeded team and a range that includes today to see a populated chart. In a new Default workspace, coverage rises as members join teams and events are logged on the Timeline.

How the number is calculated is on How coverage is calculated.