Sign in to Vector OS

Before you begin

• An eligible installed build or account page with an enabled, approved sign-in service.
• Access to the Google identity or email inbox you intend to use. Keep codes and sign-in links private.

Follow the steps

1. Start from the correct place

   For the desktop, start sign-in inside Vector OS and allow its system-browser handoff. For website access, start at the Vector OS sign-in page when it is enabled.

   Checkpoint: The sign-in attempt belongs to the intended Vector OS session; no manual token paste or arbitrary return address is involved.

2. Choose and verify your identity

   Use Google or the email-code flow offered by the service. Check the email address before requesting a code. A typed address alone is not verification.

   Checkpoint: The browser shows the identity you intended to verify.

3. Use the current code once

   Enter the code only in the sign-in flow you started. The launch design uses a 60-second resend cooldown, at most five attempts per challenge and a ten-minute challenge expiry; follow any stricter limit displayed by the service.

   Checkpoint: The service accepts the current challenge, or explains expiry/attempt limits without requiring you to share the code.

4. Wait for desktop confirmation

   After browser approval, return to Vector OS. Wait for the desktop to confirm the account and device rather than treating the browser success page as the final result.

   Checkpoint: The desktop shows the intended signed-in identity. The handoff has a five-minute attempt window; an expired attempt needs a fresh start.

5. Check the working scope

   Before sending any work, check whether you are using your personal scope or an authorized team. An invitation needs the matching verified email.

   Checkpoint: The identity and future billing scope are clear; another account's local history has not appeared.

Check the result

• The intended account is confirmed by the destination surface, including desktop device confirmation when applicable.
• Sign-in does not prove a paid entitlement, team membership or connected CAD host.

If something goes wrong

• The sign-in controls are disabled.

  Use the availability notice; do not submit credentials through a different form. The waitlist is only for requested updates.

  Resume from: Enabled approved account entry point.

• The code expires or the current challenge rejects further attempts.

  Request a new code after the displayed cooldown and use that challenge. Do not keep guessing or reuse a previous code.

  Resume from: Current email-code challenge.

• The browser completes but Vector OS remains waiting.

  Preserve local drafts. Cancel or let the attempt expire, then start a fresh attempt inside Vector OS. Do not paste credentials into a callback URL.

  Resume from: New desktop-originated handoff.

• A session expires during work.

  Sign in again without deleting local history or receipts. Already dispatched work still needs its original outcome checked.

  Resume from: Confirmed identity, then unfinished-work status.

Continue with a related guide

• Account availability
• Recover unfinished work
• Team invitations
• Privacy information