Account settings
You: your details, how you sign in, what you pay with and what reaches you.
Sign-in and security
Security in Account settings is two things: how you sign in, and a record of where and what. How you sign in lives on Personal details, under your sign-in address. The record is the Security section of the side list: Sensitive logs, Sessions and SSH keys. Verification has a page of its own.
How you sign in
Four lines on Personal details hold the ways into the account. Each opens in place, and each can be opened by its own address, so a link in an email can land on it.
Two-factor authentication
Press Turn on
Turn on first emails a code to your account address, so Xuda knows it is you.
Scan the code
A QR code appears, and the same key as text for an app on this computer. Add it to an authenticator app such as Google Authenticator, Microsoft Authenticator or 1Password.
Type the first code
Type the six digits the app shows for Xuda and press Turn on.
Keep the recovery codes
Ten single-use recovery codes are shown once. Copy them or download them, tick that you saved them, and press Done. Each code signs you in once, in place of a code from the app.
While two-factor is on, the line shows how many recovery codes are left, and warns when few are. New recovery codes replaces the set, and Turn off switches it off. Both ask for a code first. Signing in with a passkey skips the code, because a passkey is already two steps. Xuda emails you when two-factor is turned on or off and when new recovery codes are made.
Passkeys
Add a passkey asks for a code first, then for an optional name, then your device asks you to approve it. Each passkey is listed with when it was made and last used, and can be renamed or removed. A removed passkey stops signing in at once. To clear it from your device too, delete it in your password manager. Xuda emails you whenever a passkey is added.
Password
An account made with Google, a phone or a passkey has no password until you set one, and it can then sign in with its email and that password too. An account that has one changes it here. A checklist under the field ticks each rule as you meet it.
Linked accounts
Link Google account opens a Google window where you choose the account. A linked Google account signs in to this account with one press, whatever address this account has. Unlink stops it at once. Xuda emails you whenever an account is linked or unlinked.
One check before a change
Changing how you can sign in opens a way into the account, so it takes one check first, the strongest the account holds: one of its passkeys, otherwise a code from the authenticator app (or a recovery code) when two-factor is on, otherwise a code emailed to you. It applies to setting or changing the password, adding a passkey, linking a Google account, turning two-factor off or making new recovery codes, and replacing a confirmed phone number. Changing the password also signs out every other session of the account, and you are emailed.
Sessions
Sessions lists where your account is signed in: a device or a tool, its place and when it was last used, with the one you are using marked. A line at the top says how many are signed in and how many are elsewhere. Sessions you have not used for a long time are grouped in one line at the end.
Press a session to open it, then Sign out. A signed-out device has to sign in again the next time it connects. On the session you are using it reads Sign out here and takes you to the sign-in page. A session that belongs to a deployment server warns you first, because signing it out stops that server until it is reinstalled.
Sign out everywhere else signs out every session but this one, after you confirm, and keeps this device signed in.
SSH keys
SSH keys holds the public keys that may sign in to your servers, so you can give a developer access: add their key, and set an expiry if the access is temporary. Only public keys are accepted.
Add the key
Press Add SSH key. Paste the public key into SSH key content. Xuda says what it looks like, or why it is not accepted: a private key is refused. How to create one opens a guide for macOS, Windows and Linux.
Name it and set an expiry if you want one
A name tells it apart. An expiry date is optional; after it the key can no longer reach your servers. Leave it empty for no expiry.
Choose its servers
Adding a key gives it no access yet. You choose which servers it opens on each server's own Advanced page.
An open key shows its state and how many days it has left, with a meter in its last 14 days. The Access switch turns the key off: that takes it off every server it is installed on, and if it cannot be removed everywhere the key stays on and the line says how many servers refused. Delete removes the key from every server it opens, so anyone using it loses access at once, and cannot be undone. The key itself is read only: to change it, add a new one.
The Access log lists every grant, removal and expiry, newest first. Opened from a key it shows only that key, and All keys widens it.
Sensitive logs
Sensitive logs is a record of the sensitive actions on your account, newest first and grouped by day: new versions, deleted apps, domain and deploy changes, account details and server sessions. It holds your own actions and the SSH sessions on your servers. Teammates' actions are in their own logs, and sign-ins are in Sessions.
Press an entry to see what was done and how: from the dashboard, an API key, an MCP client or an SSH session. For a refusal it shows the server's sentence. Technical details fold out under it. What was sent is always shown as redacted. Narrow the list with search, date, result and event, and Export CSV saves what the filters show.
Delete logs asks first. Sensitive actions are archived: they stay on record, but leave this page. Everything else logged on your account is erased. Under a filter it clears all your entries, not only the ones shown.
Verification
Verification confirms who you are, in four levels, one under the other. Each level builds on the one before it, and you can stop at the level you need. Verification is what lets you use the parts of Xuda that need a verified account: a profile picture, a phone number, a mailbox, a domain, an API key and sharing a chat or a contact. Sending a friend request needs none of it. A request from an account whose identity is not confirmed yet shows the sender's initials, not their picture.
The level that is waiting on you opens with what to do next. If a check does not pass, you can try again; after two automatic checks that did not pass, Ask a person hands the case to the Xuda team, and a declined level can be appealed. How others see you shows your name and verification shield as other people meet them.