Notifications
mizuiro can email people when things happen - an invitation when you add someone, a calendar invite for a scheduled 1-on-1, a heads-up when a poll is shared. You decide which of those emails go out, and to whom, from Settings → Notifications.
Nothing about your own account emails changes here: password resets and sign-in confirmations always reach you regardless of anything on this page.
Before the email options make sense, mizuiro needs to know who, besides you, actually uses the app. That’s the login mode on Settings → Security:
- Just me - only you sign in. Everyone else is a record you keep; they get no emails at all.
- Me and supervisors - you and your supervisors sign in; employees are records only.
- Everyone - your whole team can sign in.
The Notifications page only appears when someone besides you signs in - there’s nothing to send otherwise. And it only offers email options for people who can actually receive them: if employees don’t sign in, the “when an employee is added” option simply isn’t shown.
At the top of the page, under Global settings, is a single switch: Send notifications.
- Off - mizuiro sends no notification emails to anyone and puts nothing in anyone’s bell. The rest of the page stays hidden. (Your account and security emails still work.)
- On - the per-scenario options appear below, and you choose which ones go out. Each one you switch on goes both by email and to the person’s bell in the app; there’s no separate in-app switch to remember, and nothing reaches the bell that wouldn’t have been emailed.
NoteEvery option starts off. Turning the main switch on doesn’t suddenly start sending everything - you pick each email you want, one at a time. mizuiro would rather send nothing, than accidentally send something.
With the main switch on, mizuiro lists every email it can send, grouped by area, each with a plain description of who receives it. For example:
- People - send an invitation when a supervisor is added, and separately when an employee is added.
- Touchpoints - a calendar invite for a scheduled one-on-one, an email to the team about a standup, a calendar invite for a formal team meeting, a reminder before it (the day before by default; set how far ahead on the Touchpoints settings page), and a note to you when someone requests a meeting.
- Polls - when a poll is shared, a deadline reminder, and the results when it closes.
- Tasks - email the person a task is assigned to when it’s created (not for a task you assign to yourself); ahead of a task’s due date (the day before by default; set how far ahead on the Tasks settings page), one nudge to its assignee (self-assigned included); and, separately, email the assignee and the person who assigned it the morning after a task’s due date passes with it still open. The due-soon and overdue emails go out once per task, not every day; move the due date and the nudge comes again.
- Time off - tell whoever’s turn it is (the supervisor of the requester’s team, or you) that a request is waiting; and, separately, tell the person who asked once it’s approved or declined, with the note.
- Policies - tell each person a policy applies to when it needs their acknowledgement (on publish, and on a reminder); and, separately, tell you 30 days before a policy is due for review.
- Incidents - email you whenever a supervisor files an incident, so nothing gets past you; and nudge whoever set a follow-up date on an incident on the morning it arrives.
- Training - a heads-up before a certification expires (30 days by default; 60 or 90 on the Training settings page), to you and, separately, to the person whose certification it is.
- Performance - a calendar invite when a review is scheduled, a reminder to the employee before it (set how far ahead on the Performance settings page), a note when a written warning is issued to them, and a note when their improvement plan is started (only once you activate it, never on a draft).
Flip on only the ones you want. Each toggle takes effect immediately.
Most of these emails can be written in your own words. Under a toggle you’ll find Customize this email, which opens two boxes:
- Top - the greeting, the first thing the person reads.
- Bottom - the sign-off at the end.
What sits between them is mizuiro’s: the details of the record, the reference number, the button, and any note about why the email was sent. That part stays put no matter what you write, so you can rewrite the whole tone of an email without ever accidentally removing the button someone needs to click.
Leave a box empty and mizuiro uses its own wording. Clear a box you’d filled in and it goes straight back to the default.
You can drop details into your text with placeholders, and mizuiro fills them in for each person as the email goes out. Click one of the chips above the boxes to insert it, or type it yourself:
| Type this | You get |
|---|---|
{name} |
The person’s preferred name, or their first name |
{first_name} |
Their first name |
{company_name} |
Your organization’s name |
{role} |
What you call their role, in your own words |
{sender_name} |
Whoever set the thing off - the person who invited them, or who booked the meeting |
So Morning {name}, something from the {company_name} team reaches
Jordan as “Morning Jo, something from the Clearwater team.”
A few emails go to a group of people at once, like a team calendar
invite. There’s no single person to name in those, so {name} becomes
“everyone” and your greeting still reads properly.
Written warnings and improvement plans always go out in mizuiro’s wording. These are formal notices that may end up being read by someone outside your organization one day, and consistent, neutral language protects both you and the person receiving it. Everything else about how you handle them is still yours.
Some records can be marked private when you create them - a private touchpoint, for instance. When a record is private, mizuiro never emails the employee about it, even if the matching notification is switched on. Marking something private is the final word; it overrides the send.
So a private 1-on-1 never triggers a calendar invite to the person it’s about, no matter how your Touchpoints notifications are set.
A short list of emails aren’t notifications at all - they’re how people get into and stay in their account, so they always send for anyone who can sign in:
- The link to set a password and finish setting up (the invitation, when the person can sign in).
- Password resets.
- Sign-in and email-confirmation messages.
These ignore the switches above by design. Turning notifications off can never lock someone out of their own account.