Skip to content

Your account

Temprix account

A Temprix account is the identity used to sign in. It is separate from membership in any particular workspace: the account is the login, and a member record is that person inside one workspace.

One account can hold members in many workspaces. Nothing is shared between them except the account itself. Roster, roles, and working patterns live on Members. Workspace administration lives on Workspace settings.


Sign-in is available with the email address the account was created with. A new account must confirm that address with a code Temprix sends by email. Passwords must be at least 12 characters. Forgotten passwords are reset from the email sign-in flow. There is no change-password flow while signed in.

Password resets are sent to the same address. Authentication emails, including verification and password reset, come from Temprix’s global infrastructure rather than from a workspace’s region.

Sign-in is also available with a Google account. The Temprix account is matched by email address, so a workspace invitation sent to a Google address links when sign-in uses that address.

If the account was created via Google, Temprix does not keep a separate password for that login. Name, email, and picture on a Google-managed account are read-only in Temprix.

SAML and OIDC are available on Enterprise, arranged as part of the agreement rather than switched on in settings. See Pricing or contact us.

Access tokens are short-lived and refreshed in the background, so an active session continues without prompting for sign-in again.

Signing out ends the session on that device. It does not affect sessions on other devices, and it does not affect API keys, which authenticate independently of sign-in.

Signing in again opens the workspace used most recently. If the account has no workspaces, Temprix prompts to create one.


The account holds name, email, and picture, used for sign-in and for the emails Temprix sends.

How someone appears inside a workspace comes from the member record in that workspace, not from the account. Display name, job title, and picture are per workspace, so the same person can be “Alexandra Novak, Support Lead” in one and “Alex” in another. Home location, work hours, and time zone are also on the workspace profile. Changing the name on the account does not change the display name inside a workspace. Which fields a member can edit is on Members.

The email address on a member record is admin-only, because it is what links that record to the account.


Preferences split by where they are stored.

Account (Settings → Account): name, email, and picture. The same everywhere the account signs in.

Workspace profile (Settings → Profile): display name, picture, title, home location, work hours, and time zone. Per membership.

Device and workspace behaviour (Settings → Preferences, and the theme control in the user menu): default home view (Teams or Members) is stored per workspace membership. Theme (light/dark/auto) and pointer-cursor preference are stored in the browser on that device and do not sync across devices.

At the API level, account-scoped settings and workspace-scoped member settings are stored separately. Member settings apply in that workspace only.


The workspace switcher lists every workspace the account belongs to. Switching changes the member record in use, role, plan, and the region the data comes from.

Each workspace has a URL of the form https://temprix.app/<namespace>/. A former namespace in a bookmark still reaches the workspace; Temprix redirects to the current one.

A workspace where the member record has been deactivated no longer appears.

A workspace admin adds someone by email address. If an account already exists for that address, the member record links to it and the workspace appears in the switcher on the next sign-in. If no account exists, one is created on first sign-in with that address.

The check for an existing account runs against Temprix’s global authentication infrastructure, whichever region the workspace was created in.

Any account can create a workspace, and the account that creates one becomes its owner. Up to 100 workspaces per account.

Creation requires a name, a data region (United States or European Union; this cannot be changed later), and a starting dataset (Default or Demo). The two choices made at creation that cannot be undone are covered on Workspace settings.


Workspace data stays in the region chosen for that workspace. Account data does not follow the same rule.

Authentication runs in a single global region, so name, email address, and credentials or Google sign-in identifier are processed there for every account, whatever regions the workspaces use. The same applies to the email lookup performed when an admin invites someone.

This is disclosed rather than incidental. The full position is in the Privacy Policy and the DPA.


Deleting an account is not the same as deleting a workspace. Leaving or being deactivated from every workspace does not delete the account, and deleting a workspace does not delete the accounts of its members.

Member records and their event history belong to the workspace, and the workspace owner is the controller of that data. Removing personal data from a workspace is a request to that workspace’s admins, covered on Members.

For the account itself, contact privacy@temprix.app. Account data is retained for 30 days after deletion to allow recovery, then permanently deleted. Retention periods are in the Privacy Policy.