Server settings
General
Branding, registration, the server catalogue and data retention.
Identity and door policy of the server, plus how long its data is kept.

Admin panel → Settings. Every knob applies instantly, no restart.
Branding
serverName textShown in the client, in emails and on the sign-in screen.
serverDescription textThe one-liner under the name on sign-in and in the server catalogue.
accentColor hex stringThe brand color, surfaced across the client UI. This is a plain text field — type a hex value such as #22d3ee; leave it empty to fall back to the built-in theme accent. (The setup wizard offers a swatch picker for the same setting; the settings tab does not.)
Registration
registrationEnabled boolean default trueWhen off, the signup form is hidden and direct registration is rejected — accounts then come only from admin provisioning or invites.
listInServerCatalogue boolean default falseWhether this server asks to appear in the public server catalogue. Only a true/false flag is exposed.
The age gate (minimumAgeYears) sits on the
Legal tab instead.
Data retention
Message, attachment and notification retention are applied by the scheduled command php bin/console tyto:retention:purge; archived channels are swept by their own scheduled task. Both need your scheduler wired up — see Operations. A value of 0 means keep forever.
messageRetentionDays days default 0 = keep foreverMessages older than this are redacted in place rather than deleted: every stored revision’s text is emptied, the message is flagged deleted, its attachments are removed and its search document is dropped. The row itself stays, so old threads keep their shape as tombstones.
notificationRetentionDays days default 0 = keep foreverNotification rows older than this are deleted outright on the same run.
archivedChannelRetentionDays days default 0 = keep foreverAn archived channel is permanently deleted this many days after it was archived — the channel, its attachments and its search documents go with it.
Retention purges are permanent — there is no undo. Shortening a period takes effect on the next scheduler run; verify your backups first.
Defaults
defaultLocale locale default enStored and editable, but the backend does not currently read it — changing it does not affect any server-rendered content today. Language is picked elsewhere: welcome messages use the community’s own locale, the daily digest uses each recipient’s locale, and password-reset / email-challenge mail follows the request’s locale. The translator’s own fallback is the APP_FALLBACK_LOCALE environment variable, not this setting.
defaultWelcomeChannelName text default generalStored and editable, but like defaultLocale nothing on the server reads it today. A community’s welcome channel is chosen per community on its Overview tab — see Welcome messages.
