Account pages

These pages belong to your Overvis HMI account rather than to one workspace. The workspace itself is described in Workspace list and settings and Workspace navigation and Setup pages. Notifications have their own page: Notifications. The steps for each task are in Manage your account and access and Manage billing.

Header and user menu

Every signed-in page has the same header, left to right:

• the menu button (on phones);
• the logo of the active workspace, or Overvis HMI when it has none for the current theme;
• the Workspaces switcher;
• the AI button, which opens the assistant;
• the theme toggle and the language switcher (inside the user menu on phones);
• the notification bell;
• the user menu.

The switcher and AI appear once your account has access and onboarding is complete.

The user menu holds, in this order:

• Report a problem: a form for a description and, optionally, one screenshot you choose. The description stays in the form if sending fails. You get a reference once the report is accepted.
• Helpdesk tickets: see Helpdesk tickets.
• Changelog: user-facing product changes, newest first. Entries are in English.
• Account settings.
• Sign out.

Where to find things

Bookmarks work for every page. Paths with $workspaceId or another $… part take the UUID of that object.

Page	Path
Sign-in	/login
Price list (no sign-in needed)	/prices
Profile and assistant spending limit	/settings
Notification settings	/settings/notifications
Passkeys, authenticator, devices, deletion	/settings/security
Sign-in email	/settings/email
Billing accounts	/settings/billing
One billing account	/settings/billing/$billingAccountId
Personal and workspace API keys	/settings/api-keys
Your account’s activity history	/settings/history
Helpdesk tickets	/tickets
Changelog	/changelog
Workspace settings	/workspaces/$workspaceId/settings
A workspace (opens its first dashboard)	/workspace/$workspaceId
A dashboard	/workspace/$workspaceId/d/$dashboardId
Alarms	/workspace/$workspaceId/alarms
A history report	/workspace/$workspaceId/reports/$presetId
Setup sections	/workspace/$workspaceId/setup/…
Activity history of a workspace	/workspace/$workspaceId/audit

The Setup paths are listed under Setup.

Workspace settings use /workspaces/ (plural); the workspace itself uses /workspace/. The assistant has no path: the AI button opens it over the current page.

Every page except /login, /invite/…, and /prices needs you to be signed in. Opening one without a session leads to /login first.

Sign-in and sessions

/login, Sign in or create an account, signs in with an email and a one-time code, or with Google or GitHub when the page offers them. A new email or provider identity creates its account through the same page; there is no separate registration and no password. If you are already signed in, the page takes you on to the app, or back to the page that sent you there.

• A passkey signs in with the device PIN or biometrics and needs no email or authenticator code.
• With authenticator protection, email and Google or GitHub sign-in also ask for the authenticator code.
• Cancelling the passkey prompt returns to the sign-in screen.

Sign-in codes:

• A code works once and for ten minutes from the request.
• Resend code becomes available after one minute. It sends a new code; only the code from the latest email works.
• Entering the email again while its code is still valid sends no new email.
• Attempts are limited, and a suspicious request can ask for a bot check. Too many attempts do not lock the account.

Sessions:

• Without Stay signed in on this device, a sign-in lasts 24 hours.
• With it, the sign-in lasts until you sign out, revoke the device under Security, recover the account, or clear the site’s cookies.
• Overvis administrators can suspend an account. A suspended account cannot sign in or use either kind of API key.

Onboarding and access

After the first sign-in, /onboarding asks for your name and company name (required), your role at work, and your industry. During the closed beta you also confirm that data may be deleted and breaking changes may occur before the public release. New accounts take their notification language from the app and their time zone from the browser.

During the closed beta, an account needs access before it can use workspaces:

• /beta explains this, takes an Access code, and gives the sales contact sales@overvis.com. An access code grants access for good.
• An invitation to a workspace grants access too.
• Until then, the profile, notification, security, and email settings, account deletion included, are available. Billing, API keys, and History are not.

Once onboarding is complete and the account has access, its first workspace is created from the company name, unless the account came through an invitation: then it enters the inviting workspace.

Invitations

An invitation link (/invite/…) opens with or without a session.

• An invitation to the email of an existing account adds it to the workspace at once, with the invited role. The account gets an email with a link to the workspace instead of an invitation link.
• A new invitee signs in with the invited email on the same page and completes onboarding, then enters the workspace.
• If another account is signed in, the page names the account needed and offers Switch account.
• If the signed-in email is not verified, Sign in with an email code signs in and returns to the invitation.
• An invitation expires after seven days. An expired or revoked invitation does not work; a workspace admin or owner can send a new one.

Account settings

Account settings has the tabs Profile, Notifications, Security, Email, Billing, API keys, and History. Notification settings are described under Notifications.

Profile

Name, company, position, and industry. Name and company are required. Changing them does not rename workspaces.

The Assistant spending limit card sets Limit per task, EUR (empty for no limit) with Save limit. See Cost and spending limit.

Security

• Passkeys: add and remove passkeys.
• Authenticator app: Enable authenticator shows a QR code, a link for an app on the same device, and the setup key. It needs a code from the app and confirmation that you saved the recovery codes. Download codes saves them as a text file. Each recovery code works once.
• Connected login methods: Google and GitHub. Connecting one never changes your account email. If the provider’s email matches an existing account, you confirm the connection after signing in to that account. You can disconnect your only provider; email sign-in stays.
• Signed-in devices: your sessions. Revoking one signs that device out. When Overvis support opens a session on your account to help you, it appears here as Local administration impersonation and can be revoked like any other device.
• Account deletion; see Account deletion.

Fresh verification

Changes to sign-in methods, the email, API keys, signed-in devices, and recovery codes, and account deletion, ask you to verify again, even on a remembered device. The browser then stays verified for two hours, so several changes in a row need one verification.

• With authenticator protection, verify with an authenticator code, a recovery code, or a passkey. Email alone cannot remove that protection.
• Without it, verify with an email code or a passkey.
• Recovery codes do not authorize email changes, API-key changes, or account deletion.

Recovery

• Signing in with a recovery code signs out your other sessions and forgets remembered devices.
• After such a sign-in, Security offers to generate new recovery codes. For five minutes the recovery sign-in authorizes one security change, so even your last recovery code can authorize its replacement. New codes invalidate the previous set.
• A passkey can also authorize replacing a lost authenticator.
• Support at support@overvis.com or the helpdesk can help investigate a lost authenticator but cannot bypass authenticator protection.

Account deletion

Deletion needs fresh verification. The dialog lists what it removes:

• every workspace you own, disabled ones included, with its data for every member;
• every billing account you are the last owner of. A positive balance is given up, not refunded, and you confirm that separately. See Deleting your account.

If either list changes before you confirm, the dialog shows it again. In workspaces owned by other people, your membership is removed, and your comments and activity records stay without your identifying details.

Email

Changing the sign-in email needs fresh verification and a code sent to the new address. The current email stays until the new one is verified. Resend code works after one minute. Once confirmed, your other devices are signed out, and pending workspace invitations to the new email are accepted.

Billing

Billing lists every billing account you are a member of, your personal one first, with your role, the balance in EUR, and its low-balance alerts. The concepts are explained in Billing accounts.

• Owners and managers get Top up (on regular accounts), Redeem voucher, and Alerts.
• Details opens the account’s page.
• /settings/billing?voucher=<code>, the QR code on a printed voucher, opens Redeem a voucher with the code filled in.

Billing account page

Every member of the account sees all tabs; what they can change depends on their role.

Tab	Shows	Actions
Overview	Balance and the negative limit; spend in the last 24 hours and 7 days; how many days the balance lasts at recent spending; spend per day for 30 days with the costliest kinds of usage	Owners and managers: Top up, Redeem voucher, Alerts. Owners: Rename
Usage	Charges of the last 7 or 30 days, this month, or last month: total and daily average, per day, per kind of usage, and per workspace with the items that used the most (endpoints, API keys, users, assistant chats, dashboards, files, automations, alarm rules)	Storage charges link to the workspace’s Setup → Stored data
Ledger	Every change of the balance, by day in your time zone. Hourly charges are summed per workspace and kind of usage; top-ups, vouchers, refunds, and corrections are listed one by one	Export CSV
Members	Members and their roles: owner, manager, viewer	Owners: Add member, change roles, remove. Everyone but the last owner: Leave

An item’s amount on Usage is its estimated share of the workspace’s charge for that kind of usage; the totals per workspace and kind match the ledger.

Limits and rules

Topic	Rule
Card top-up	At least 10 EUR, in whole euros. The dialog shows the largest top-up and the largest balance a top-up may reach. Stripe emails a receipt; there is no invoice for a card top-up
Payment confirmation	The balance updates once Stripe confirms the payment, usually within seconds; some payment methods take longer
Voucher code	12 letters and digits, printed in groups of four, such as ABCD-EFGH-JKMN. Case, spaces, and hyphens do not matter. The code has no 0, O, 1, I, or L
Voucher attempts	After 10 refused attempts within 15 minutes by one person, or 20 for one billing account, further attempts are refused until the 15 minutes are over
Ledger export	Up to 366 days per file, oldest entry first, amounts in EUR. When the period has too many entries, the file holds the first ones and says so

Low-balance alerts

Alerts has two alerts, each with its own switch. They go to the account’s owners and managers, on the channels their notification settings allow.

Alert	Field	Default	Sent when
Warn when recent spending leaves few days of balance	Days left, 1–60	7	The balance lasts fewer days at recent spending
Warn when the balance falls below an amount	Amount in EUR	0	The balance falls below the amount; it stays as a banner until dismissed

• Recent spending is the higher of the last day’s spend and the last week’s daily average. An account that spends nothing gets no days alert.
• The amount cannot be lower than the account’s negative limit.
• Each alert is sent once when the balance crosses it, and again only after a top-up or another credit has raised the balance back. Saving an alert checks it again from then on.
• During the beta, alerts are not sent.

API keys

API keys lists both kinds of key. Neither kind signs in to the browser app. What each kind can reach is under API authentication.

• Personal API keys: keys you create here for scripts and API clients. Each acts with your permissions in every workspace you belong to. The full key is shown only once, when you create it. The list shows each key’s name, prefix, and creation time.
• Local workspace keys: workspace API keys, created when you pull a workspace with Develop locally. Each reaches only its one workspace. The list shows the workspace and, when known, the machine.

Creating and revoking keys needs fresh verification. A revoked key stops working at once; a local workspace that used a revoked workspace API key needs a new pull.

History

History shows your account’s own activity history. Under Deleted workspace history it links to the history of workspaces you owned before they were deleted.

Helpdesk tickets

/tickets lists the Helpdesk tickets your account filed: number, title, category, status (New, In progress, Closed), and creation time. The number opens the ticket’s private Helpdesk page. Anyone with that link can read the ticket and comment on it.

The form below takes a category (Technical problem, Feature request, Device setup and support, or Billing question), a title, and a message. File Helpdesk ticket files it. The assistant can file a ticket too, after showing you the same fields to confirm. Files are attached on the Helpdesk page.

Prices

/prices shows the price list in effect, VAT included, what each kind of usage counts, and scheduled price changes with the time they take effect. Prices per day are shown per month of 30 days. No sign-in is needed. See What is charged.

Related docs

• Manage your account and access
• Manage billing
• Billing accounts
• Notifications
• Workspace list and settings
• Workspace roles