personal settings

Manage basic account information, notifications and preferences, and security settings. After logging in, click "Profile" in the left navigation, or visit /profile directly.

Basic information

Basic information

Change the bound email address

Fill in new email address

Fill in the new email address to be bound in the email input box

Send verification code

Click the "Send" button

Complete binding

Enter the verification code you received and click "Bind Email"

Change password

Change password

Fill in the current password, new password, confirm new password, and click "Change Password" to complete the change.

Change password

Two-factor authentication (2FA)

After turning on 2FA, you need to enter the dynamic code in the authenticator app in addition to the password each time you log in, which effectively prevents account theft.

Two-factor authentication

Turn on 2FA

Install the authenticator app

Install the authenticator app on your phone (Google Authenticator or Microsoft Authenticator recommended)

Start setting up

Find the "Two-factor authentication" area on the personal settings page and click "Turn on 2FA"

Scan the QR code

Use the validator app to scan the QR code displayed on the page, and a 6-digit dynamic code will appear in the app

Verify and enable

Fill in the 6-digit dynamic code displayed in the App into the verification box and click "Confirm to Open"

Save backup code

The system displays a set of backup codes. Please take a screenshot or copy and save them immediately for emergency login when the authenticator cannot be used.

2FA QR code
⚠️ Backup code reminder
The backup code is only displayed once and cannot be viewed again after closing the pop-up window. When you lose your backup code and cannot use the authenticator, you need to contact the administrator to reset it.

Notification settings

Configure the method and trigger conditions for receiving system notifications on the "Settings and Preferences" tab.

Notification method

The following notification channels are supported, and you can choose according to your needs:

channelDescription
EmailReceive notifications via email
WebhookPush to custom webhook interface
BarkPush to Bark (iOS push app)
GotifyPush to self-built Gotify server

Configure notifications

Choose notification method

Select Email / Webhook / Bark / Gotify in "Notification Method"

Set quota warning threshold

Enter a value in the "Quota Warning Threshold" and receive a notification when the balance falls below this value.

Set notification email

Fill in the email address to receive notifications in "Notification Email". If left blank, use the account email.

Save configuration

Click "Save Settings" to complete the configuration

Settings and preferences

Preferences

Configure account behavior preferences in the "Preferences" area of the "Settings and Preferences" tab, and click "Save Settings" after modifications to take effect.

Accept unpriced models

Controls whether calling models without configured prices is allowed. When it is turned off, it refuses to call the unpriced model (recommended). When it is turned on, it can use the unpriced model.

⚠️ NOTE
Allowing unpriced models may result in unexpectedly high consumption and is recommended to be kept turned off.

Log IP address

Controls whether the source IP address of API calls is logged in usage and error logs. After turning it on, you can view the source IP of each call in the usage log, making it easier to monitor abnormal access and troubleshoot security issues.

Security settings

Reset API access token

If you suspect that your API access token has been compromised, you can reset the token:

Find security settings

Find the "Security" area on the personal settings page

Open access token

Click on the "Access Token" card

Copy new token

The system automatically generates a new token and the old token becomes invalid immediately.

Regenerate access token
⚠️ IMPORTANT NOTE
After resetting the API access token, all existing tokens will become invalid and the API access token will need to be re-created. All applications using old tokens need to update their configuration.