Announcements

Announcements are banners Sluicio shows to users — a maintenance window, a deprecation notice, a “we know, we’re on it” during an incident. They are published from Settings → System → Announcements by the install operator, and they are cell-wide: every user on the install sees them as in-app banners. Since a cell serves a single organization, there is one announcement surface — no per-org scoping.

Each announcement has a message, a severity — info, warning, or critical, which styles the banner — an optional expiry after which it stops showing, and a dismissible flag. Dismissing an announcement in-app is per-user and server-side: it stays dismissed for that user on every device.

Maintenance windows automatically publish their own announcement for their duration — those are managed from the maintenance window itself (Alerts → Maintenance), not from the announcements form.

If your Sluicio instance is run for you rather than by you, announcements belong to whoever runs it: there is no operator on such an instance, so the form is theirs and not yours.

Announcements on the login page

By default, announcements only appear inside the app — which is no help when the announcement is “logins are about to break”. Since v0.11.35, the announcement form (Settings → System → Announcements) has a Show on login page checkbox. Flagged announcements also render as severity-styled banners on the sign-in page, before anyone authenticates — so a maintenance or outage notice reaches users exactly when they can’t get in.

The flag is off by default on every announcement; you opt each one in.

Because the login page is unauthenticated, it fetches flagged announcements from a public endpoint that returns a deliberately minimal payload: the message, its severity, and whether it’s dismissible — nothing else. Write flagged announcements accordingly: anyone who can reach your sign-in page can read them.

Dismissal works differently on the login page

• In-app, dismissing an announcement is per-user and server-side — it stays dismissed for that user on every device.
• On the login page, there’s no user yet, so dismissal is per-browser (stored in localStorage). The same person sees the banner again in another browser or a private window, and clearing site data brings it back.

For a notice that must not be missed — “logins will be unavailable Saturday 02:00–04:00 UTC” — consider making it non-dismissible for the duration.