Notifications and reports
Settings → Notifications. Every email Sekee can send, grouped by category, each with its own switch.
:::info Plan Email notifications are available from the Starter plan upwards. :::
How they are decided
Three things have to be true for an email to reach you:
- You are an audience for it — a participant, a follower, a mentioned person, or somebody it was addressed to
- The preference is on — either because you switched it on, or because that type is on by default
- You are not the person who caused it — the actor is always dropped from the recipient list
A comment is saved whether or not the email about it goes out. Notifications never fail the thing that triggered them.
Following things
Besides the switches, you can watch individual things:
| Watch | And you are told about |
|---|---|
| A bug hunt | Comments, bugs and status changes on it |
| A session | The same, for that session |
| A folder | Test cases added anywhere beneath it |
| An automated test | State changes on it |
| A Milestone | Its readiness flipping between Ready and Not ready |
Watching a folder covers the whole subtree — following Checkout also
catches Checkout / Payments.
:::note Recently changed Watching a Milestone is new, and works the same as watching a bug hunt. Its email has its own rule on top of the three above: at most one per Milestone per hour, even if readiness flips back and forth in that window. The preference lives in a new Milestones category, on by default. :::
Watching is never gated on edit permission.
Mentions
Typing @name in a comment notifies that person, on a test case, a bug hunt
case, a session note or an automation run. They get a notification in the bell
and, except on an automation run, an email if they have mention emails on. Editing a comment to add a mention
notifies nobody; a mention counts when the comment is first posted.
Sekee sends mentions itself. The comment is posted with the people it names, and Sekee writes the notification and the email from the saved comment, so the same thing happens whether you wrote it in the app or an AI assistant wrote it through the AI connector. Only active members of your organization are told, never the person who wrote the comment, and no more than 20 for one comment; a mention of anybody else is quietly ignored and the comment is still saved. A comment written through the connector names its author as (AI generated) in the email, as it does in the app.
One comment sends you one email. If somebody mentions you in a comment on a test case you wrote, you get the mention email and not the "new comment on your test" email as well. With mention emails switched off, you get the comment email instead.
:::note Recently changed Until release 1.1.0, the author of a test case who was mentioned in a comment on it got both emails.
The person who owns the test case is only spared the "new comment" email when Sekee actually sent them the mention email. If they were left out of it — they have been blocked, or the comment named more than 20 people — they still get the comment email, so nobody ends up with none. :::
:::note Recently changed Mentions used to be sent by your browser, one request per person. Sekee now sends them from the server, and the browser no longer can. A page that was already open when this release arrived loses all mentions — test case, bug hunt, session and automation run — until you reload it, because it still tries the old way and Sekee now refuses that. The comment itself is always saved. :::
Periodic reports
Four reports, each independent, each off by default:
| Report | Covers |
|---|---|
| Daily | Today so far, against the same point on the last working day |
| Weekly | Last week against the week before |
| Monthly | Last month against the month before |
| Quarterly | Last quarter against the one before |
They arrive at 16:00 in your time zone, and the windows are cut in your zone too, so the day a report names is the day you lived through.
The daily report arrives every weekday, quiet ones included: a day with nothing recorded is still a report, with every figure at zero. The other three are sent when there is something to say (see below).
:::note Recently changed Reports were not being delivered. A scheduling fault meant none of the four was ever sent, however it was set. If you switched one on and never received it, nothing was wrong with your settings, and it arrives from now on.
The daily report no longer skips quiet days. It used to be left out when nothing had been recorded that day or the working day before, which made a quiet week and a broken report look the same. Production and staging may be on different versions, so one of them may still behave the old way. :::
:::note The daily report changed recently It used to cover yesterday against the day before. It now covers today so far, compared against the same point on the previous working day — Monday against Friday, not against a Sunday nobody worked — and it is not sent at weekends.
The comparison uses the same slice of that day rather than all of it. At 16:00 the current window is sixteen hours, so measuring it against a full twenty-four would report a fall every single afternoon. :::
Why you might not be getting one
In rough order of likelihood:
- The report is off. All four are off by default. Turn it on here.
- Your time zone is unset, so you resolve to UTC and the report arrives at 16:00 UTC rather than 16:00 your time. Set it on your profile.
- The period was quiet, for the weekly, monthly and quarterly reports. One with nothing in either window is not sent — a first quiet period is a real signal and is reported, a second is just an email that teaches people to filter the sender. The daily report is sent regardless.
- It is the weekend, for the daily report.
- Your organization has no members subscribed to it, so nothing is assembled at all.
Security emails you cannot turn off
A handful of emails ignore every preference on this page, because they are the only warning an account takeover produces — and an attacker who reached your settings could otherwise switch the warning off on the way past:
- Two-factor authentication turned on or off
- New backup codes generated
- A backup code used to sign in
- An owner or admin reset your two-factor
- You signed out your other devices
- A password reset you asked for
"A new device signs in to my account" is not in that list — it has a switch on this page, and it is on by default.
Product updates and What's new
Now and then the Sekee team writes about what is new in Sekee: what the update is, then what changed in it, under New, Improved and Fixed. Those emails are on by default: the New features and product news switch, under Product updates on this page. They reach every plan, guests included. Every one ends with Turn this one off, which opens a page where Yes, stop them switches them off without signing in, and Gmail and Outlook can show an Unsubscribe button beside the sender that does it in one click.
The same news is in the app, on the What's new page in the sidebar, with a count beside it when something has arrived since you last looked. An email's Read it in Sekee opens that announcement's own page there. The rare one kept out of What's new says Open Sekee instead.
A service notice is different: it is about the Service itself — billing starting, a change to the terms — and goes to everyone it is addressed to, whatever this page says. It has no link to turn it off. It is marked Service notice, in the email and in What's new.
Either kind can be addressed to owners and admins only, and then reaches nobody else.
:::note Recently changed Product updates and What's new are new. :::
Turning one off from the email
Every notification's footer links straight to the switch that produced it. That link is stable and points at the exact row on this page. A product update's Turn this one off is the exception, opening the page described above instead, and a service notice has no links, because it cannot be turned off.