Skip to content
Maliru Help Center

Updates and announcements

One-to-many posts built in two steps, with required reads that chase themselves and a record of who confirmed.

Updates are your announcements: one message to many people, landing in each person's feed and inbox. They live under Communications › Updates, and on the phone under Chat › Updates. Posting needs the Manage chat permission. Anyone can read, react, comment and confirm.

Posting an update

Post update (on the phone, the + button) opens Create an update:

  • Create from scratch: "Compose a new update with a live field-user preview."
  • Start from a template: search the ready-made ones (Start-of-shift briefing, Safety notice, Weather and site notice, Procedure change) and any marked "Saved by your team".

Create an update: from scratch or from a template

The builder then runs in two steps:

  1. 1 of 2 · Compose: the Update title, the message, its Appearance, Rich content (images, files, links, YouTube, shortcuts into Maliru) and an optional Live poll, with a Field-user preview beside it. Publish settings moves on.
  2. 2 of 2 · Publish: Publish now or Schedule, the Audience (Everyone, a Team, an Access profile or a Smart Group), whether to notify people, who it shows as, an unviewed reminder, a required confirmation, comments and reactions, repeating, pinning and automatic removal. Publish update (or Schedule update) sends it. Back to compose returns to step 1.

Every option is explained in Composing an update. Save as template keeps the wording for next time.

Required reads and confirmations

For anything that must be seen, such as a safety notice or a policy change, switch on Confirmation › Require each recipient to confirm read in step 2. Each recipient gets a Confirm read button, which turns to Confirmed once pressed. On the phone, an unconfirmed update also appears on Today, for example "1 update to acknowledge".

The card tracks progress as "{n}/{total} confirmed" and "{n}/{total} viewed". With Manage chat, click the confirmed count to see person by person who has viewed and who has confirmed.

The chase runs by itself. 24 hours after publishing, everyone who hasn't confirmed gets one "Please confirm: {title}" notification, and the author is told how many are left, for example "3 people have not confirmed: {title}". The author is never reminded or chased by their own update. This is separate from the Unviewed reminder, which sends "Reminder: {title}" to people who haven't opened the update at a time you choose.

The feed

The Updates feed with a pinned required-read notice and a poll with votes

  • Pinned updates sit at the top with a pin mark. A scheduled update shows Scheduled until it goes out.
  • Depending on how the update was set up, people can React, Comment and vote in its poll.
  • Comments accept @ mentions. You can name anyone the update went to, its author, or people with Manage chat, and they are notified. See Mention someone on a job, defect or other record.

With Manage chat, each card's menu has:

  • Pin or Unpin.
  • Archive, which takes it out of the feed and keeps it.
  • Delete update: "Its comments, reactions and confirmations go with it. This cannot be undone."

Updates aren't emailed. Notifications go in-app and by push, and the builder says "Email delivery remains deferred."

Tip: save Require each recipient to confirm read for things that genuinely need a signature. Overuse it and confirmations become noise. Keep it for safety and policy and the acknowledgement trail stays meaningful.

For a meeting or toolbox talk with named attendees and signatures, use Briefings and attendance registers. A confirmed update records that each person read it. A briefing register records who attended a session.