Global Settings
Global settings apply across the entire HoMeeSuite instance. Only Superadmins can access them at Admin → Settings.
Email (SMTP)
HoMeeSuite sends transactional email for account verification, password resets, shift confirmations, reminders, and broadcasts. All outbound mail goes through a single SMTP configuration.
Configuring SMTP
Navigate to Admin → Settings → Communication and fill in:
| Field | Description |
|---|---|
| Host | SMTP server hostname (e.g. smtp.mailgun.org, email-smtp.eu-west-1.amazonaws.com) |
| Port | Typically 587 (STARTTLS) or 465 (implicit TLS) |
| Username | SMTP authentication username |
| Password | SMTP authentication password |
| From address | The sender address shown on all outgoing mail (e.g. noreply@your-domain.example.com) |
SMTP settings entered here override any values set in the environment .env file.
Sending a test email
After saving, use the Send test email button to send a verification message to your own address. If delivery fails, the error is shown inline — check your credentials and make sure the SMTP port is reachable from the server.
Common providers
| Provider | Host | Port |
|---|---|---|
| Mailgun (EU) | smtp.eu.mailgun.org |
587 |
| AWS SES (eu-west-1) | email-smtp.eu-west-1.amazonaws.com |
587 |
| Postfix (self-hosted) | localhost or your server hostname |
25 or 587 |
| Mailtrap (staging) | sandbox.smtp.mailtrap.io |
587 |
Email not delivering?
- Confirm the SMTP credentials are correct using the test-send button
- Check that your server can reach the SMTP host on the configured port (
telnet <host> <port>) - Verify the from address is an authorised sender on your mail provider (SPF / DKIM alignment)
- For Mailgun and AWS SES, ensure the sending domain is verified and not in sandbox mode
Favicon
Superadmins can upload a custom PNG or ICO favicon (max 1 MB) at Admin → Settings. It replaces the default browser-tab icon and takes effect within about 60 seconds. Use the Reset to default option to restore the built-in icon at any time.
Logo
Superadmins can upload a custom PNG, JPEG, or WebP logo (max 1 MB) at Admin → Settings. The logo appears on the public landing page header and in the app sidebar, and takes effect within about 60 seconds. SVG files are not accepted. Use the Reset to default option to restore the built-in mark and app name at any time.
Admins can also set the logo display height (16-64px, default 28) — the logo scales proportionally by height so wide banner-shaped logos are not distorted into a square. A "Show app name next to logo" toggle controls whether the app name appears beside the logo; the app name always shows when no logo is configured.
Notification channels
Push (Web Push)
HoMeeSuite can send browser and OS-level push notifications for shift reminders, broadcasts, and urgency alerts. Configure it at Admin → Settings → Notification Channels → Push (Web Push) (superadmin only, requires admin:settings:write).
| Field | Description |
|---|---|
| VAPID public key | The key browsers bind their subscription to. Safe to expose — it is never treated as a secret. |
| VAPID private key | The server-side signing key used to authenticate outgoing push messages. Stored encrypted at rest and never displayed again after saving — the field is always blank when you open the page. |
| VAPID contact | A mailto: address or https:// URL push services use to reach the operator if there's a problem. Any other prefix is rejected. |
The fastest path: click Generate new keys, confirm, done — no command line needed. Operators who prefer to supply their own keypair can still run npx web-push generate-vapid-keys and paste the values in manually.
Rotation warning: generating new keys or pasting a different public key signs every device out of push, and each person has to switch push back on from their own profile. This is the one irreversible action on the page — say so plainly if you're walking someone else through it.
Environment-variable precedence: VAPID_PUBLIC_KEY / VAPID_PRIVATE_KEY / VAPID_SUBJECT seed the channel when no database row exists yet. Push settings entered here override any values set in the environment .env file, and take precedence from then on — the same pattern as SMTP settings.
Propagation: changes take effect immediately in the web app and within about 60 seconds in the background worker, because each process caches channel configuration independently.
Troubleshooting: if volunteers report the push switch on their profile is greyed out with a message that push is not configured for this deployment, this section is the fix — no VAPID configuration exists yet.
Landing Page FAQ
The Landing Page FAQ section lets you manage FAQ items that appear on the public landing page. FAQ items are global — they are not tied to a specific event.
Managing FAQ items
Navigate to Admin → Settings and scroll to the Landing Page FAQ section.
- Add an item: Click Add FAQ item, enter the question and answer, then click Save. The answer field supports markdown formatting (bold, italic, bullet lists, links) via the toolbar with a Write/Preview toggle; the question stays plain text.
- Edit an item: Click the Edit button on any row to update the question, answer, or visibility.
- Toggle visibility: Use the Visible on landing page switch inside the edit form to hide an item without deleting it.
- Reorder: Use the ↑ and ↓ buttons to change the display order on the landing page.
- Delete: Click Delete on a row and confirm the prompt.
Only users with the admin:settings:write permission can create, edit, or delete FAQ items.
Footer Links
The Footer Links section lets you manage the links shown in the public landing page footer. Footer links are global — they are not tied to a specific event — and use a free-text label and URL, so you can rename or replace any link (privacy, imprint, docs, external links) without a code change.
Managing footer links
Navigate to Admin → Settings and scroll to the Footer Links section.
- Add a link: Click Add footer link, enter the label and URL, then click Save.
- Edit a link: Click the Edit button on any row to update the label, URL, or visibility.
- Toggle external: Use the External link (opens in new tab) switch to control whether the link opens in a new tab.
- Toggle visibility: Use the Visible in footer switch inside the edit form to hide a link without deleting it.
- Reorder: Use the ↑ and ↓ buttons to change the display order in the footer.
- Delete: Click Delete on a row and confirm the prompt.
Only users with the admin:settings:write permission can create, edit, or delete footer links.
Legal Pages (Datenschutz / Impressum)
The Legal Pages section lets you edit the German-only Datenschutzerklärung (privacy policy) and Impressum (imprint) shown at the public, unauthenticated routes /datenschutz and /impressum. Content is Markdown and is rendered through the same sanitized pipeline as the documentation pages.
Navigate to Admin → Settings and scroll to the Legal Pages section. Edit either text area and click Save — changes appear on the public page immediately. Before any admin edit, both pages already show drafted seed content, so they are never blank.
Only users with the admin:settings:write permission can edit these pages.
This supersedes the earlier guidance of adding a Footer Links entry pointing at an externally-hosted privacy/imprint page — the footer already links to /datenschutz and /impressum by default.