Skip to main content

Accounts and sign-in

Use normal TestVibe accounts for both daily work and administration.

Choose a sign-in method​

  • Start with a local email/password account. Add GitHub, Google, Microsoft Entra ID, or an OpenID Connect provider in Settings → Administration → Sign-in when your team needs it.
  • Workspace owner/admin roles and instance-administrator access are separate. Grant installation-wide access only through Administration → Administrators or host recovery.

Local accounts​

  • The first local signup on an unclaimed installation creates the administrator without email verification. Later signups follow Administration → Registration.
  • Invite teammates from Settings → Members. Configure Email for password resets and normal verification messages.
  • No standard admin password is installed or documented. Lost administrator access is recovered through the host console.

Public address and callbacks​

  • Set the canonical Application URL under Administration → Addresses, or in your deployment configuration if host-managed.
  • Register the callback URL required by each provider using that public HTTPS address. Keep the protocol, hostname, port and path consistent with the provider configuration.

Connect an identity provider​

  • Enter the provider’s client ID and secret. For OpenID Connect, also enter the issuer, display label and scopes.
  • Save the section and restart when the screen requests it. Test a separate browser session before relying on SSO for the team.
  • Keep a recoverable local administrator available while changing identity settings.

Microsoft Entra ID is available from 0.4.16 as a dedicated, tenant-specific provider. Supply your tenant GUID, application client ID, and client secret. Use your organization’s tenant rather than a shared common or organizations endpoint.

Account ownership​

  • Use your verified email consistently when connecting identities. Review account linking in your profile.
  • A workspace role never automatically grants instance administration. Removing or suspending the last active instance administrator is blocked.

Recover access​

  • Check the public URL, callback registration, provider credentials, clock and network reachability when SSO fails.
  • Use host recovery to reset an instance administrator if normal sign-in cannot be restored. The temporary password must be replaced on the normal login screen.