Server settings
Advanced
Auth-code and invite expiry, the digest hour, media token lifetimes, the HTTP cache and server bot roles — plus the knobs that have no UI at all.
The catch-all tab: short-lived credentials, the daily digest schedule, signed-media lifetimes, the HTTP cache, and which bot account plays which server role.
Authentication codes
validateEmails booleanRequire users to confirm their email address before they can sign in.
resetPasswordCodeExpiryMinutes 1–1440How long a password-reset code stays valid after it’s issued.
emailChallengeExpiryMinutes 1–1440Same, for the one-time code in an email-confirmation challenge.
invitationExpiryHours 1–720 default 72How long an admin-issued account invitation stays usable.
Notifications
digestHour 0–23 (UTC)Hour of the day the daily email digest is dispatched — per-user opt-in, rendered in each recipient’s own language.
Media token lifetimes
Files are never served from a public bucket — every link is signed and expiring:
mediaTokenTtlSeconds secondsHow long signed URLs for attachments, avatars and logos remain valid.
communityEmojiTokenTtlSeconds secondsSame for custom emoji images — safely much longer, since emoji rarely change. Emoji URLs use bucketed signing so timelines full of :shortcodes: stay cacheable.
Longer TTL = browser caches work harder; shorter = a revoked member loses media access sooner. The size and format limits for the same files are on the Uploads tab.
HTTP cache
A shared cache in front of the most-read endpoints: message pages, pinned messages, threads, custom emojis, community details and online counts. It is on by default in production and needs no setup.
- Per viewer, not per token. Responses are stored per access context — anonymous, member, or a viewer whose roles and groups change what they see — so people with the same access share one entry and private content never reaches anyone else. Tokens are hashed into the lookup key and never stored or echoed back.
- Fresh after changes. Sending, editing, deleting, reacting, pinning and channel or community changes clear the affected entries straight away. Online counts are the exception: they only expire on their TTL.
- Bots and API keys bypass it. Requests made with an API key always reach the server, so per-key scopes are checked on every call.
- Emptied on every update, so a new version never serves pages cached by the old one.
The section starts locked: tick I know what I am doing to edit the
values, and saving asks for confirmation. Disable HTTP cache fills in
0 for all three; save to apply it.
httpCachePageTtlSeconds seconds default 3600How long message pages, pinned messages, threads, emojis and community details are served from the cache. Never longer than mediaTokenTtlSeconds, so cached pages never carry expired image links. 0 turns this part off.
httpCachePresenceTtlSeconds seconds default 15How long community online counts are cached. They can’t be cleared early, so keep this short — the client asks every 30 seconds. 0 turns it off.
httpCacheContextTtlSeconds seconds default 600How long a viewer’s access lookup is reused, so cache hits skip the application entirely. Cleared as soon as roles, groups, memberships or bans change. 0 looks it up on every request.
The cache lives in its own http-cache Valkey container, capped at 256 MB and dropping the least-used entries when full (HTTP_CACHE_MAXMEMORY). To empty it by hand, see Operations.
Bot roles
Bot accounts (created in admin → Users) can hold server roles:
defaultBotIdThe server’s general-purpose bot identity, used for system messages when a role has no bot of its own.
welcomeBotIdPosts localized greetings in communities’ welcome channels.
autoModeratorBotIdIssues the automatic timeouts.
Unassigned roles fall back to the default bot; with no bots configured the related features quietly do nothing.
Settings with no UI
One more group exists in the registry but has no field on any tab.
Webhooks
These three are not in the admin API either — set them directly in the settings store:
webhookMaxQueued integer default 1000 not in admin UICap on deliveries buffered while an endpoint is disabled. Once a disabled webhook has this many queued deliveries, new events are skipped — the buffer already collected is kept intact for replay, not rotated.
webhookLogRetentionDays days default 30 not in admin UIHow long delivery attempts stay inspectable in the admin panel.
webhookAllowInternalUrls boolean default false not in admin UISSRF guard, shared with web-push endpoints — enable only to deliberately target services on the server’s own network.