Skip to content

Sign in and recover access

Open the Eyerobot application using your organization’s usual entry point. Available sign-in choices depend on which methods the service has enabled; a missing signup or social button is not an invitation to use another workspace’s account.

Use your existing email/password when that is your account’s method. Google/GitHub buttons appear only when enabled. Follow the chosen provider’s sign-in and return to Eyerobot.

Matching email addresses do not automatically merge accounts. If Eyerobot asks whether to create a new enterprise or associate a sign-in method with an existing account, choose deliberately. Existing-account association requires signing into that account and confirming the association.

Email signup begins with verification. Follow the received verification link, review the verified address and complete the requested enterprise name/password. Social registration can instead request the enterprise name after the provider step. Where plan selection is enabled, a selected paid plan is reviewed after registration; the account keeps its initial free rights until payment is confirmed.

Requesting an email does not prove it has arrived, and a generic confirmation does not disclose whether an address already has an account. Do not repeatedly create workspaces to work around an uncertain completion; check ordinary sign-in first.

Use Forgot password when offered. Request the recovery email, follow its link and submit the new password. After confirmed reset, return to ordinary sign-in. Existing human connections are revoked by the reset; it does not automatically sign you in.

A social-only account does not gain a local password merely by requesting recovery. Use an available established method and the actual account feedback.

Signing in and membership in a customer enterprise are separate. If no project is visible, check membership and project access with an administrator. Account recovery does not change your enterprise role or undo a removed assignment.

Single-user offer restrictions can prevent invitations even for an administrator. Review plans and the actual enabled account controls and Plan and usage. Payment commands remain enabled separately; a selected paid plan or browser return is not proof of paid activation. A support inbox is a separate feature.

Do not include verification/reset links, passwords or sign-in screenshots containing proofs in a public support example.