Notifications (Benachrichtigungen)

The Notifications page is where you compose and review broadcast messages to your own staff — short alerts that appear in the bell icon at the top of the dashboard for everyone logged into your tenant. It is not the place where automated guest emails are configured; those rules live on the Automatische Nachrichten and E-Mail Vorlagen tabs of Settings, and this page links them together at the end.

Use Notifications to surface things every team member should see the moment they open CampOne — a quick “front desk closed for lunch”, a price change taking effect today, an incident note that should not get lost in chat. Each notification has a severity (info, warning, error, success) that controls the colour of the dot in the bell list, and each can carry an optional link.

How to find it

In the sidebar, open the Einstellungen (Settings) group and click Benachrichtigungen (Notifications). The link is visible to tenant_admin and superadmin only — staff users cannot see it. There is no entry in the user-menu footer.

What is on the page

The page is split into two sections stacked vertically. A page title at the top, then a compose card, then a history table. There are no tabs.

Compose section

A card with the form for sending a new notification.

• Title — required, up to 200 characters. The headline of the notification.
• Body — optional, up to 2000 characters. Free-text detail. Plain text only; line breaks are preserved.
• Severity — one of:
  • info — neutral blue dot, default for general announcements.
  • warning — yellow dot, for situations that need attention but are not urgent (“system maintenance tonight”).
  • error — red dot, for incidents (“payment terminal down”).
  • success — green dot, for positive announcements (“season target reached”).
• Link URL — optional. If you provide a valid HTTP(S) link, recipients can click the notification to open it. Use this to deep-link into a specific booking or report.
• Preview pane — a live render that shows what the bell entry will look like as you type. The dot colour follows the severity selector.
• Send button — fires the notification immediately. Once sent, the notification cannot be edited; you can only resend a copy or delete it.

History section

A reverse-chronological table of the last 50 notifications you have sent. Columns:

• A coloured dot showing the severity.
• Title.
• Timestamp, formatted in your locale.
• Recipient count (how many staff users were targeted at send time).
• Actions: Resend and Delete.

The history is shared across your tenant — every tenant_admin sees the same list. Staff users only see the in-bell notifications, not this admin view.

Where automated guest messages live

Sending an automated email to a guest when their booking is confirmed, or an SMS the day before arrival, is not done from this page. Those rules are on:

• Settings → Automatische Nachrichten — the rules that define triggers (“on booking confirmed”, “X days before arrival”, “after departure”), the channel (email, SMS, in-app) and which template each rule uses.
• Settings → E-Mail Vorlagen — the wording of each transactional email, with subject, plain-text body and HTML body. Templates use {{placeholders}} for guest name, dates and booking reference.

Together these two tabs are the equivalent of a “notification rules” engine. The Notifications page in this reference is the lighter-weight, staff-only broadcast tool that sits next to it.

Common workflows

Tell the team the payment terminal is down

1. Open Notifications.
2. Title: Worldline terminal offline.
3. Body: short instructions — “Take cash or TWINT only until further notice. ETA on fix: 16:00.”
4. Severity: error.
5. Click Send. Every staff bell icon lights up red within seconds.

Announce a closure with a link

1. Compose a new notification.
2. Title: Front desk closed Friday afternoon.
3. Body: short explanation.
4. Severity: warning.
5. Link URL: paste the URL of the rota entry or planning doc.
6. Send.

Re-broadcast yesterday’s safety notice

1. Find the notification in the history table.
2. Click Resend. A new entry appears at the top of the list with a fresh timestamp; the old one stays put for the audit trail.

Delete a notification you sent by mistake

1. Find the entry in the history.
2. Click Delete. Note: deletion removes the row from the admin history and from staff bells. There is no undo.

Set up an automatic email after every booking confirmation

This is not done on this page. Instead:

1. Open Settings, switch to Automatische Nachrichten.
2. Add a rule with trigger “On booking confirmed”, channel “Email”, and pick the confirmation template.
3. Save.
4. If you also need to edit the wording, switch to E-Mail Vorlagen, open the matching template, edit subject and body, and use Vorschau senden to mail yourself a sample.

Set up an arrival-reminder SMS three days before check-in

Same approach as above, on the Automatische Nachrichten tab — pick the “X days before arrival” trigger, set the offset to 3 and the channel to SMS. SMS delivery is only available if your plan includes it.

Tips and gotchas

• Broadcast notifications go to all staff in your tenant. There is no per-role or per-user targeting on this page; everyone with a CampOne login at your campsite will see them.
• A notification with no body is allowed but unhelpful. Always include at least one sentence.
• The link URL field does only basic validation — it must start with http:// or https://. Internal CampOne paths (for example a booking detail) need their full domain.
• Resend does not edit; it sends an exact copy. To correct a typo you have to delete and re-send.
• Delete is final. There is no archive.
• The history list only shows the last 50 entries; older notifications drop off and cannot be recovered through this UI.
• Guests never see broadcast notifications. They only receive the automated emails / SMS configured under Settings.
• If you need a notification rule for a particular booking event (“send a reminder when balance is unpaid 7 days before arrival”), use the Automatische Nachrichten tab — broadcast notifications cannot be triggered automatically.
• Severity is only a visual cue; it does not change delivery, escalation or recipients.

Related pages

• Settings — the Automatische Nachrichten and E-Mail Vorlagen tabs handle automated guest messaging
• Roles and permissions — only tenant_admin and superadmin can see and use this page
• Sidebar tour — where Notifications sits among the other admin entries
• Help — if you need to contact CampOne about a delivery problem with automated messages