Settings

Settings is the admin area for panel-wide configuration — a set of pages in the sidebar, each covered below.

📷Settings → the admin configuration pages.img/settings.avif

Email

Configure the SMTP server SpipCP uses to send invites, password resets, and monitoring alerts. Email settings are stored encrypted, and login never depends on email — so a broken mailer can't lock anyone out.

📷Email — SMTP host, credentials, and a test send.img/settings-email.avif

→ Detail: Setup wizard.

DNS providers

Named DNS credentials — Cloudflare, Bunny, Hetzner, deSEC, or Gcore — that let SpipCP create DNS records automatically when a domain is attached. The API token is encrypted and never reaches a node, and an account can be set as a default that cascades node → instance → domain. To run self-hosted nameservers instead, see the DNS section.

→ Full page: DNS providers.

SSL issuers

Alternative certificate authorities for HTTPS — ZeroSSL or Actalis (ACME with EAB) and self-supplied custom certificates. Let's Encrypt is the default and needs no account. Secrets (EAB HMAC keys, private keys) are encrypted and never reach a node; the chosen issuer cascades node → instance → domain.

→ Full page: SSL issuer accounts.

Secrets

The encrypted secret store. Secrets are kept encrypted, and revealing one is audited, so there's a record of every time a secret was viewed.

📷Secrets — the encrypted store, with audited reveal.img/settings-secrets.avif

Git accounts

Reusable provider credentials (GitHub, GitLab, Bitbucket, Gitea) used to browse repos and register deploy keys. The token stays in the panel and never reaches a node.

→ Full page: Git accounts.

Locality

The panel's default timezone and locale, plus per-user overrides — so timestamps and formats read the way each person expects.

📷Locality — timezone and locale, panel default and per-user.img/settings-locality.avif

→ Detail: Locality.

Changelog

Not a Settings page but its own item in the Admin group: where a release is written — version, severity, summary, and items tagged new / improved / fixed — saved as a draft and published in one click. A draft is invisible everywhere until published. Publishing can notify users in-app and by email (each user can turn release email off in their own preferences; it is on by default), and POSTs a signed webhook to anything listening.

📷Compose a release — version, severity, and the items. The commits baked into the image are offered as a starting point, to be reworded.img/changelog-compose.avif

Delivery is configured on Settings → Changelog: the webhook endpoints that get every published release (signed with HMAC-SHA256, the same scheme as the probe webhooks), and mirror mode — pointing the panel at a canonical feed makes it render that changelog instead of its own blank one. Mirroring is off by default, and off means no outbound request at all.

📷Settings → Changelog — signed webhooks, and mirroring a canonical feed.img/settings-changelog.avif

Published releases become the public feed the docs changelog renders.

→ Consume it: Changelog API. · What the numbers mean: Versioning.

Audit log

The append-only record of accountable actions — who did what, when. Also reachable from Activity in the sidebar.

→ Full page: Audit log.