Skip to content
BlogStart for free

Account

Secure your account and manage sessions

Use Security settings to manage sign-in and active sessions. Set up an authenticator and keep a working recovery method before changing how you access your account.

  1. Open Settings → Security.
  2. Enter your current password.
  3. Enter a new password and its confirmation.
  4. Follow the displayed rules: at least ten characters, an uppercase letter, a lowercase letter, a number, and at least three unique characters.
  5. Choose Save and check the confirmation.

If you have forgotten the current password, use password reset from sign-in. For an external-provider account, use the available sign-in route and the controls supported by that account.

  1. Open Settings → Account → Linked accounts.
  2. Choose Connect for the provider.
  3. Sign in to the provider and authorize the connection.
  4. Return to Buildryn and verify it is connected.

Connecting from a signed-in account associates the provider with that account. Confirm you are authorizing the intended Google/GitHub identity.

Check that another usable sign-in method is available, then choose Disconnect for the linked provider. The application can refuse removal if it would leave no permitted sign-in route.

Disconnecting a provider in Buildryn changes that account link; it does not delete your Google or GitHub account.

  1. Open Settings → Security and choose Enable 2FA.
  2. Open an authenticator app on your device.
  3. Scan the displayed QR code, or enter the manual setup key.
  4. Enter the current six-digit code from the authenticator.
  5. Choose Verify & Enable.
  6. Save the recovery codes shown afterward using the download option or another private storage method.
  7. Confirm I’ve Saved My Codes only after retaining them.

Expected result: after signing in with your password or provider, you must complete the required authenticator verification.

Keep the setup key and recovery codes private. A QR screenshot is also sensitive because it contains the authenticator secret.

If you cannot access your authenticator, select the recovery-code option and enter an unused saved code. Keep recovery codes private and use each one once.

Once you regain access, restore your normal authentication setup and check remaining recovery codes. If you have neither the authenticator nor a usable recovery code, these instructions cannot bypass account verification.

  1. While signed in, open Security.
  2. Choose Regenerate Recovery Codes.
  3. Complete any verification requested.
  4. Save the new codes and remove your stored copy of the old set.

Replacement codes supersede the previous set. Update your stored copy so you do not rely on obsolete codes during an emergency.

Choose Remove Authentication from Security and complete the application’s verification/confirmation flow. Check the resulting state. Disabling 2FA changes future sign-in checks; it does not remove an external provider or change your password.

Open Active Sessions in Security. Review the displayed device, browser/operating system, IP/activity information, and Current indicator where available.

Use these details to identify your own browsers and devices. Network addresses can change. Compare the device, browser, activity, and IP address before deciding whether you recognize a session.

  1. Find the session you want to end.
  2. Choose Revoke and complete any confirmation.
  3. Check that it is no longer listed as active.

Use Revoke all other sessions to end other sign-ins while retaining the current one. If you do not recognize activity, also review your password, linked accounts, and two-factor setup.

Sign out normally when leaving a shared computer. Revoking a session stops that sign-in’s continued access; it does not delete projects or subscription records.

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.