Platform admin

A platform admin runs the deployment itself. The role passes every check — every workspace, every project, every setting — so it is held by few people. It is separate from being a workspace admin.

Who is a platform admin

  • The first account registered on a deployment is the platform admin. On a fresh self-hosted OpenV, register first and that account is it.
  • A platform admin makes others: open Platform admin from the account menu (top right), find the person under Platform admins (or in Usage, By person) and click Make admin. Remove takes it away again. You cannot remove your own standing, and the last platform admin cannot be removed.

Somebody who cannot get back into a password account — the reset email did not arrive, the address was mistyped, or the server sends no mail at all — asks you. In the Platform admins table, every password account has a Reset link button. Confirm, and the page shows a link once: copy it and pass it to the person however you talk to them. It works once, expires after 24 hours, and lets whoever holds it set a new password for that account, which signs the account out everywhere. Because the link did not go through the person's inbox it proves nothing about their address, so hand it to somebody you have identified. Each link you make is written to the server log with your account. Accounts that sign in through Google or single sign-on have no password, so they have no button.

Usage

The Usage section shows how much each workspace and each person uses OpenV, and whether that use is speeding up or slowing down. It shows counts only: how many requirements, test cases, links, test runs and comments a workspace holds, and how many changes are made each week. It never shows what an artifact says, its title or its reference.

  • By workspace groups workspaces by plan, then company workspaces before personal ones, busiest first. Each row shows the members who signed in in the last 30 days out of all its members, what it holds, a bar per week for the last 12 weeks, its pace and when it last changed. Click a workspace's name to see its members under it, each with their own pace. People opens By person filtered to that workspace.
  • By person lists everyone. Filter by plan, by workspace (narrowed to the plan you chose), by pace, or search by name or email. Each person shows their workspaces and role in each, the days they signed in in the last 4 weeks, their weekly changes, their pace and when they were last seen. Make admin and Reset link are here too.

Pace compares the last 4 weeks with the 4 weeks before. A rise of a quarter or more is Accelerating and a fall of a quarter or more is Slowing; anything between is Steady. New means activity lately and none before, Gone quiet means activity before and none lately, and No activity means none in either. A change is anything a person or an agent did that shows in a project's Activity; jobs the system runs itself do not count. A person who only reads is paced on the days they signed in. Hover a badge to see the two totals it compares.

Workspaces and plans

The Workspaces table (in Usage, By workspace, once your release has the usage view) lists every workspace on the deployment with its type, plan and members. Change a plan from the selector: a plan decides the workspace's limits and its default release channel. A workspace you move from Single User, Business Lite, Self-hosted or Open source onto Business or Enterprise stays on the nightly channel, as it would after a checkout, so none of the features its members use switch off; its admins can choose stable in its settings.

The Open source plan is how an open-source project is hosted free: choose it and every project in that workspace is published, as of its latest baseline, on the site's open-source page. Live work stays private until the next baseline. The page asks you to confirm before it changes a plan.

The same change is available from the command line for scripts: PUT /api/v1/orgs/<id>/plan {"plan": "open_source"} signed in as a platform admin.