Skip to Content
Using HelmSign in, change email and sign out

Product guide

Sign in and leave safely

Create an account, manage email and password access, and distinguish local logout from signing out everywhere.

Use your email and password to access Helm. New reviewers can create an account from the public entry page. Social login is upcoming, so use the working email/password controls today.

Create an account or sign in

  1. Open Helm and choose the sign-in or account-creation option.
  2. Enter your own email and password.
  3. Follow the resulting guidance. If confirmation is requested, complete it before assuming the account is signed in.
  4. Once you enter Helm, check that you are viewing your own account before recording money.

A request being accepted is not proof that an email arrived. If confirmation or password recovery mail does not arrive, check spam and the address you entered, then use the available retry or contact the person operating your Helm instance. Do not create repeated accounts to work around a missing message.

Change your email

Open Settings → Account and sessions. Follow the email-change controls, including the current-password check. Your existing verified address remains meaningful until the change is confirmed. Use the result shown by Helm rather than assuming the request immediately replaced your sign-in address.

Choose the right sign-out action

  • Sign out ends the local browser session when it succeeds.
  • Sign out everywhere, under Settings → Account and sessions, requests retirement of your sessions on other devices too.
  • Leave this browser clears local credentials and private cached state when that recovery option is offered. It does not claim other devices were signed out.

If the provider or connection refuses a logout, read the result and retry. Local cleanup and confirmed global sign-out are different outcomes.

On a shared browser

Sign out or use the offered leave-browser action before handing the device over. Back navigation should not reveal the previous private view. If you see stale private content after a session change, close the view and report that behavior using safe details; never continue entering another person’s data.

API-token access is separate from a browser session. Manage integration credentials under API tokens and revoke a token you no longer need.