Personal settings
Your personal settings control how you appear in Radd, how sign-in works for your account, and your personal API tokens. Open them from Settings → Profile and Settings → API tokens.
The Profile page holds your name, avatar, and timezone.
| Setting | What it does | Default |
|---|---|---|
| Display name | The name shown on your comments, assignments, and mentions. | Your account name |
| Avatar emoji | An emoji shown instead of your initials. | None |
| Avatar color | The background color behind your initials or emoji. | A color derived from your account |
| Timezone | Stored on your account and shown on your profile. | Browser default |
To change your name, avatar, or timezone, edit the fields and click Save profile.
Radd stores your timezone but does not yet use it to display dates and times. Every date and time in the interface follows your browser's clock, not the timezone on your profile.
The top of the Profile page. The Leave, Notifications, AI assistance, Two-factor authentication, and API tokens sections continue below.
Two-factor authentication adds a one-time code from an authenticator app to sign-in. It applies only to sign-in with an email and password. An account that signs in through SSO or a directory keeps its provider's own multi-factor check instead.
Radd has no recovery code for two-factor authentication. If you lose your authenticator device after you turn it on, you cannot remove the code yourself. Contact whoever administers your Radd server — they can clear the setting for you outside the product.
To turn on two-factor authentication:
- Click Enable.
- Add the secret, or the full otpauth URI, to an authenticator app (Google Authenticator, 1Password, Aegis, or a similar app) as a time-based (TOTP) entry.
- Enter the 6-digit code the app generates.
- Click Confirm and enable.
At your next sign-in with your email and password, Radd asks for a code from your authenticator app after your password. Enter the current code to finish signing in.
Radd requires a current code to turn two-factor authentication off, so a stolen session cannot remove it silently. To turn it off, click Disable…, enter a current code, then click Confirm disable.
Appearance holds your theme (Dark or Light) and density (Normal or Compact). Click a button to switch immediately.
Radd stores theme and density in your browser, not on your account. They do not follow you to another browser or another machine — each one keeps its own choice.
The Notifications section on the Profile page sets which events reach your inbox, and which of those also reach you by email.
Each event type has two boxes: Inbox and Email. Email needs the inbox box checked — a muted event never reaches your inbox, so there is nothing to email. If you uncheck Inbox for an event, Radd also unchecks Email for it.
An Email digest of unread notifications checkbox at the bottom sends a digest that includes anything you were not emailed about individually.
An API token is a personal credential for scripts and integrations. Radd
sends it as an HTTP header: Authorization: Bearer radd_pat_…. A token
acts with your own permissions — it can do anything you can do, and nothing
more.
The interface does not offer a way to narrow a token to fewer permissions than your account. Every token you create carries your full access.
Radd shows the full token text once, right after you create it. You cannot see the full text again after that. Copy it before you dismiss that message.
To create a token:
- Open Settings → API tokens.
- Type a name under New token.
- Optionally set an expiry date. Leave it empty for a token that never expires.
- Click Create token.
- Copy the token text shown, then dismiss the message.
If you lose a token's text, you cannot recover it. Revoke the token, then create a new one.
You cannot undo a revoke, and a revoked token stops working immediately. To revoke a token, click Revoke on its row, then click Confirm revoke.
TODO(verify): whether there is a limit on how many personal tokens one account can hold.
Mirrored from project.radd-hq.com on 2026-09-12. Documentation is written there; this copy is regenerated by scripts/publish_wiki.py and hand edits do not survive it.