Vetrix Docs

Account

Account pages cover everything that belongs to you personally rather than to a repository: getting into Vetrix in the first place, how you appear to other people, the credentials that let your computer and your scripts act on your behalf, and which events reach you. They apply to every account on the instance, whatever your permissions elsewhere.

Where to find it: the registration, sign-in, and password-reset pages are public and reached from gitvetrix.com/login. Everything else lives in your personal settings: open the account menu from your avatar in the top-right corner of any page, choose Settings, and pick a page from the Account group in the settings sidebar.

Getting into your account

Create an account, sign in, and recover access if you are locked out.

  • Password reset — request a reset link by email and use it to set a new password, with the confirmation worded so it never reveals which addresses are registered.
  • Registration — create an account with a username, email, and password or a sign-in provider, then confirm your email to activate it.
  • Signing in — sign in with your username or email and password, enter a two-factor code when your account requires one, or continue with a configured provider.

Your details and notifications

Control how you appear across the site and which events reach you.

  • Notification preferences — use the grid of events and delivery channels to turn in-app and email notification on or off for each event independently.
  • Profile — set your display name, bio, and email address, upload or remove your profile photo, and copy your user ID.

Credentials and security

Add the second sign-in step, and manage the keys, tokens, and applications that authenticate as you.

  • OAuth applications — register the applications that call the API through the OAuth2 authorization-code flow, copy and rotate their credentials, and review a consent screen before you authorize it.
  • Personal access tokens — create a named, optionally expiring token, choose the scopes that limit what it can do, copy its one-time value, and revoke it when it is no longer needed.
  • SSH keys — add the public half of a key pair so Git operations over SSH work without a password, review the keys on your account, and remove one you no longer use.
  • Two-factor authentication — turn on the authenticator-app code prompt, save single-use backup recovery codes, turn it back off, and change your account password.