Start here
First login and email
Create an administrator, retrieve email verification codes and prepare outgoing delivery.
On this page
Sign in locally
Open /manage/login?_locale=en on your CMS host. Use the email and password you created, then retrieve the verification code from Mailpit at port 8025. The CMS has no shipped default password. The terminal hides password input during administrator creation. You may not see characters or dots while typing. If you forget the password, use the email-based reset flow rather than editing database hashes by hand.
Mailpit and real delivery
Mailpit captures local messages. It does not deliver them to a real Gmail or practice mailbox. Keep it private, and use fictional recipient addresses for demonstrations. For a real deployment, configure a TLS-capable SMTP provider privately. The default environment transport can be supplemented by the administrator's verified SMTP settings. Provider-specific app passwords or OAuth requirements still apply.
Verify a new SMTP configuration
Open Settings → Writing. Enter the provider details, confirm with your current CMS password and send a verification test. A six-digit code is sent only to the signed-in administrator. Enter it within ten minutes; five attempts are allowed. The old mail transport stays active until verification succeeds. Stored credentials are encrypted and are not displayed in password fields. Changing the CMS configuration does not create a mailbox or set SPF, DKIM or DMARC records.
Recovery prerequisites
- Preserve your private environment configuration and the matching integration encryption key.
- Confirm that login, invitation and password-reset emails reach the intended account before go-live.
- Never disable verification to work around broken email delivery.
- Production email delivery and retries need dedicated acceptance testing; local tests do not establish deliverability.
Something unclear? Contact me about this guide.