Account and help

Account and security

Manage profile details, email verification, password sessions, and connected sign-in methods.

Manage your profile

Open Profile from the account menu to change:

  • display name and avatar;
  • email address.

The account menu also lets you choose the interface language, light/dark/system theme, and notification sound. Sound is on by default; the saved account setting applies to all projects and is used when you sign in on another device. You can also change it with /sound in project chat.

Choose an available interface language, or System to follow your browser language. Product help and documentation follow the selected language.

Your preferred model and reasoning level are also saved in your account. Choose them below the message field on Home or in project chat; the same preference is used across all project chats and when you sign in on another device. Availability depends on the applicable plan. See Agent and chat.

An email change remains pending until the new address is verified. Project invitations also require an active verified account and must be accepted with the exact invited address.

Profile groups personal details, account emails, password controls and sign-in connections into separate cards under the relevant tabs. Each card keeps its own save or update action.

Phone number

Email registration requires an email address and a phone number. Confirm your email using the link sent to your inbox; the phone number is entered manually without SMS verification. External sign-in requests available email and phone details, but missing contact data does not block sign-in. Registration credits are granted once when the account is created. Adding a phone or signing in again does not grant another bonus.

Existing accounts keep their saved contact details and do not need to register again.

If the sign-in page asks you to use a provided account, enter the email and password supplied by your administrator. Registration and the other public account-access pages are unavailable there; contact your administrator if you need access or a password change.

During registration, select your phone's country and enter the number using the displayed mask. Enter your password once and confirm your agreement with the linked documents before submitting.

Password and recovery

An account with a password can change it from Profile after entering the current password. A successful change revokes the current session and returns the browser to sign-in. Password reset through the recovery flow revokes earlier sessions. If another page starts returning authorization errors after a security change, sign in again instead of repeatedly retrying an expired session.

Connected sign-in methods

Google is available for quick sign-in and registration. You can also connect it in your profile.

Profile lists the available external sign-in providers. Link a provider through the explicit connection action. A provider returning the same email as an existing password account does not silently merge the accounts. Amazi prevents disconnecting the final usable sign-in method, so add a password or another provider before removing the only connection.

Sign in to Amazi Desktop

Amazi Desktop is available for Windows and Linux. Sign-in uses your browser and the available Amazi login methods, without separate email or password fields in Desktop. See Connected devices for installation and access settings.

Updated required documents

Amazi may ask you to review updated required documents before continuing. Open the linked documents, select the required confirmations, and choose Continue. A notice can explain what changed. Your existing account does not need to be registered again.

Keep access safe

Personal API tokens let your automation read and manage project chats. Create, list and revoke them through the API operations described in Amazi API. Tokens have their own expiration and permissions. Logging out does not revoke them; revoke an unused or exposed token explicitly. Already accepted work continues after revocation.

Never send the following in chat or support messages:

  • passwords or reset links;
  • session tokens or provider codes;
  • integration credentials or project secrets.

Use the dedicated protected form for each value. Log out revokes the current session; if Amazi reports that logout failed, do not assume the session ended. Retry when the API is reachable, or close access from a trusted device after changing the password.