Notifications

Where do I see my notifications?

The bell icon in the top bar shows your unread count. Select it for a quick look at your most recent notifications without leaving the page you're on — choose any item to jump straight to what it's about, choose Mark all as read right there to clear everything without opening the full page, or choose View all to open the full Notifications page. When you're all caught up, the popover simply says so.

The bell keeps itself up to date while you work — you never need to reload the page to see a new notice. It checks again every time you open it (what you were already looking at stays on screen while it does), when you come back to the tab, and about once a minute while the tab is open. Marking things read on the full Notifications page updates the bell straight away, too.

Each item in the popover shows its full title (wrapping onto a second line when it's long, so a meeting's name isn't cut off on a phone) and the first line of its details underneath. Choosing an item that doesn't link anywhere simply marks it read.

Open Notifications to see them all, newest first. Whenever something on your board needs your attention or changes — a meeting, a vote, a task, a document, and more — a notice shows up here. Each unread item is clearly marked; choose Mark as read on one, or use the button at the top of the page to clear several at once.

That button always tells you exactly what it will clear. With no filter applied it reads Mark all as read and clears every unread notice. Narrow the list first — to Unread, or to a single type — and it changes to say so and counts what it will touch, for example Mark these 3 as read: it clears only the notices you're looking at and leaves the rest unread. So filtering to Vote requested and choosing Mark these 3 as read never quietly clears your meeting reminders. If nothing in the current view is unread, the button isn't offered at all.

The bell popover's own Mark all as read is the unfiltered one: it always clears everything unread, because the popover isn't a filtered view.

Opening a notice marks it read for you. Choosing one — from the bell popover or from the Notifications page — takes you to what it's about and clears it from your unread count at the same time, so the bell stops counting things you've already dealt with. Mark as read is still there for the notices you want to clear without opening them.

Read something you actually meant to come back to? Choose Mark as unread — it sits right next to Dismiss on any already-read notice — and it returns to your unread count and list right away, exactly as if it had just arrived. Read/unread works both ways, the same as dismiss/archive does: opening a notice, or choosing Mark as read, is never a one-way door.

Done with a notice for good? Choose Dismiss to archive it — it disappears from the list and the bell right away, and a brief Undo offer lets you bring it straight back if that was a mistake. Archiving never deletes anything: switch to the Archived chip any time to see everything you've dismissed and choose Restore to bring one back into the main list. Archived notices don't count toward your unread badge, and mark-read never touches them — which is why the mark-read button isn't shown at all while you're in the Archived view.

Every notice carries an icon and a short label for its kind — Meeting reminder, Meeting started, Meeting cancelled, Meeting moved, Agenda published, Packet ready, Vote requested, Vote result, Minutes circulated for review, Minutes published, Correction suggested, RSVP requested, Task assigned, Task due soon, Task completed, Due date changed, Survey response requested, Survey due soon, Document out for review, Comments due soon, New draft for review, Review closed, Comment deadline changed, Review comment reply, Please acknowledge, Recording uploaded, Added to a committee, Seat assigned, Term changed, Term ended, Term ending, Terms ending soon, Role changed, Invitation accepted, New discussion post, Mentioned you, Acknowledgment reminder, Note reply, Availability requested, Poll scheduled, Poll needs a decision, You're presenting, or Project owner — so you can tell at a glance what each one is about.

Each notice's timestamp — in the bell popover and on the full page alike — renders in your board's own time zone (Settings → Board profile), the same as every other date and time in the app; hover or focus it to see the same instant in UTC.

Finding the notice you want

Notifications are grouped by when they arrived — Today, This week, and Earlier — so recent activity stays at the top.

Above the list are filter chips:

• All / Unread / Archived — show everything active, only what you haven't read yet, or the notices you've dismissed.
• By type — narrow to a single kind (for example, only Vote requested). Each type chip shows how many notices of that kind you have in the current view, so you know before you click whether it's worth opening.

The chips you pick are remembered in the page address, so a filtered view is easy to bookmark or share as a link. Choosing Unread (or a type chip, or both together) actually narrows what's counted and paged, not just what's drawn on the current screen — so "Showing 1–43 of 43" under Unread means exactly 43 unread notices exist, paged correctly across as many pages as it takes, never a page that comes up empty partway through. Choose Clear filters to go back to the full list.

The number in the page header ("You have 43 unread notifications in total") is a different, deliberate thing: your unread count across everything, regardless of which chip or type you currently have selected. It won't match the count in a type-filtered or Archived view below it — that's expected, not a bug — the header is always the whole-inbox total, and the "Showing X–Y of N" line below the chips always describes exactly what you're looking at. The mark-read button beside that header follows the filtered view, not the header number: it counts and clears only what the chips have narrowed you down to.

Paging through older notifications

The Notifications page tells you exactly where you stand — a line above the list reads something like "Showing 1–50 of 137 notifications" when nothing is filtered, or "Showing 1–20 of 43 unread notifications" once you've chosen Unread — so the count and the list you're looking at never quietly disagree with each other.

Once you have more notices than fit on one page, Previous page / Next page controls appear below the list. Archived pages the same way as the main list, and switching pages never forgets which chip (All / Unread / Archived, or a type filter) you had selected — the page number, like every other filter, lives in the page address, so a link to page 2 of your unread or archived notices is exactly as shareable as a link to page 1, and you'll never land on a page that turns out empty because a filter thinned it out.

Choosing what you receive

At the bottom of the Notifications page is a Notification preferences section — a simple grid where you decide, for each kind of notice, whether it reaches you in-app, by email, both, or neither:

Every topic in that grid is backed by a notice the system really sends — there are no settings here that switch nothing. In particular, packet-ready notices go out when an administrator finalizes a board packet and chooses Notify the board, and minutes published notices go out the moment minutes are approved.

One notice deliberately has no row in the grid: the Acknowledgment reminder an administrator sends with the Send a reminder button on a governing document's acknowledgment roster (see Documents). It's a direct, targeted ask about a specific outstanding obligation — not a subscription — so it always reaches you in-app; only its accompanying email follows your own email opt-in.

What a recording notice looks like

The moment a meeting recording finishes uploading and is verified playable, everyone invited to that meeting — the sitting board, or the committee for a committee meeting — gets a Recording uploaded notice, except the person who uploaded it. That deliberately includes members who couldn't attend: the recording is how they catch up. The notice links straight to the Recording card on the meeting page, where the recording plays in place and is marked New; the email version carries a Play the recording button to the same spot — it still lands there if you have to sign in first. Turn these off (in-app, email, or both) with the Recordings row of the preferences grid.

What happens when I'm added to a committee?

You're told, immediately: an Added to a committee notice in the bell — named for the committee, and saying so plainly when you were made its chair — plus the matching email with a View the committee button. Whoever added you is never notified of their own action, and adding yourself notifies nobody. Removed and later re-added? That's a genuinely new membership, so you're told again. The Committees row of the preferences grid turns these off per channel, like everything else.

What does the Your membership topic cover?

Notices about your own place on the board, and about the people you bring onto it:

• Seat assigned — an administrator put you on a seat ("You've been seated as Treasurer, Jan 1, 2027 – Dec 31, 2028"). Choose it to open your profile, which lists your terms.

• Term changed — an administrator corrected your term's seat, start date, or end date. It says exactly what changed, old → new ("End date: Dec 31, 2027 → Dec 31, 2028."), because moving your end date also moves your Term ending reminders. Saving a term without changing anything sends nothing.

• Term ended — an administrator ended your term, with the date it ended ("Your term as Treasurer ended on Oct 1, 2026."). Not sent if you've already left the board (resigned or removed).

• Term ending — your term on a seat ends in 60 days, and again at 14 days ("Your term as Treasurer ends on Dec 31, 2026. Talk to the chair if you plan to stand again."). Counted on your board's own calendar. Not sent if you've already been re-appointed to the same seat, your term is open-ended, or you're no longer serving.

• Terms ending soon — for administrators and the chair only: one weekly roll-up of every term ending in the next 60 days that nobody has been re-appointed to yet, linking to Seats & terms. Never more than one a week, and none at all in a week with nothing ending.

• Role changed — an administrator changed your board role. It names your old and new role and says what the new one can do. You're never notified about a change you made to your own role.

• Invitation accepted — someone you invited accepted and joined the board ("Jane Doe accepted your invitation and joined Acme Board"). Choose it to open their profile. It goes to whoever sent the invitation; if that person has since left the board, the board's administrators are told instead (or the chair, on a board with no administrator). You're never told about an invitation you accepted yourself, and each invitation is announced once.

You're never told about a seat or term change you made to your own term, and each change is sent once. Adding someone as a new member straight onto a seat doesn't send Seat assigned — their invitation is their first word from the board.

See roles vs. positions and seat and term notices for more.

Everything is switched on by default, so you never miss anything until you choose to. Tick or untick the In-app and Email boxes for each topic and choose Save preferences. For example, you can keep the in-app vote reminders but turn off vote emails — the two are independent. On a phone the grid stacks into one card per topic, each with a full-width In-app and Email row, so there is nothing to scroll sideways and nothing fiddly to tap.

These preferences are personal and apply only to your account on this board. Each board you belong to has its own set, and no one else — not even an administrator — can change them for you.

Below the grid is one more, separate checkbox: Include a calendar file with meeting invites. It isn't a grid column because it only concerns meetings — unlike everything above, it doesn't decide whether an email arrives at all; it decides whether a meeting invite, reschedule, or cancellation email also carries a calendar file that lands on your own calendar app automatically. Turn it off and you still get the same email with its link back to the meeting; nothing is added to your calendar for you. It's on by default and saves together with the grid. See do meetings land on my own calendar automatically? for the full picture, including what clicking Accept/Decline in your calendar app does and doesn't do today.

What happens when a meeting is scheduled

The moment a meeting is scheduled — for the sitting board, or the committee roster for a committee meeting — every invited member gets an RSVP requested notice: an item in your bell and, unless you've turned the Meetings topic's Email box off, a branded invite email with a View meeting button. This is the notice that tells you a meeting exists at all, so it's sent the moment scheduling happens, not just when the meeting is later moved or cancelled.

Your in-app and email choices for Meetings are consulted separately, the same as everywhere else in the grid: turn the email off and you still see the notice waiting for you in the bell; turn the bell off and you still get the invite email. Re-scheduling the same meeting sends an updated invite email (honoring the same Meetings email preference) but doesn't add a second bell row for it — a reschedule's own Meeting moved notice is what tells you on the bell that something changed. See what the board hears when a meeting is cancelled or moved and do meetings land on my own calendar automatically? for the rest of the calendar-invite lifecycle.

Your weekly digest

Once a week you get a single Your weekly board digest email — a short round-up of what's coming up and what still needs you, so you can catch up without logging in. It's an email only; the digest never adds anything to your bell.

It gathers exactly three things, and only the ones that are genuinely yours:

• Upcoming meetings — meetings scheduled to start in the next seven days. Committee meetings appear only if you're on that committee, and a meeting you've already RSVP'd No to is left out.
• Open votes — motions and written-consent rounds that are still open and that you haven't voted on yet. Once you've cast your ballot, or the consent round's deadline passes, it drops out. Only members who hold a voting seat are asked.
• Tasks due — action items assigned to you that are already overdue or fall due within the next seven days. Tasks you've marked Done or Cancelled never appear, and neither do other people's tasks.

If none of those apply to you that week, no email is sent at all — you'll never get an empty "nothing to report" digest. And you only ever get one digest per week: if the system retries, it won't send you a second copy.

Every date and time in the digest is shown in your board's time zone (Settings → Board profile) — or, for a meeting held in a different zone, that meeting's own zone, named so it's unambiguous. Whether a task counts as "overdue" is judged against your board's calendar day too, not the server's.

The digest follows the same email contact switch as every other message from your board: if an administrator has turned email notifications off for your member record (or your address has bounced and been suppressed), no digest is sent. It isn't one of the topics in the preferences grid above — those govern individual notices as they happen, while the digest is the weekly summary of what's still outstanding.

What a packet-ready or minutes-published notice looks like

Both arrive the same way: an item in your bell and on the Notifications page, and — unless you've turned that topic's Email box off — a branded email with a button straight to the document.

• Agenda published — "The agenda for meeting on date is up", sent when an organizer publishes the agenda and leaves Email the board that the agenda is up ticked. It lists the first few items and links to the meeting's Agenda page. Republishing never sends it again.
• Packet ready — sent once per finalized packet version. In the app it links to that meeting's Packet page. The email has two buttons: Read in browser opens the packet straight from the email, on any device, with no sign-in, and Download PDF opens the PDF file itself. See Open it straight from the email. Finalizing the same version twice never notifies you twice. A second or later version reads Board packet updated and says which version it replaces.
• Minutes published — sent when minutes are approved, linking to that meeting's Minutes page. If minutes are reopened for a correction, nothing is sent for the reopening itself; you're notified again only when the corrected minutes are approved.
• Correction suggested — sent to the member who circulated a draft when a reviewer suggests a correction to it (or to the board's minute-takers, if nobody is recorded as circulating it), quoting the suggestion and linking to the Suggested corrections panel on the minutes page. See suggesting a correction.

Your in-app and email choices are consulted separately, so muting the email still leaves the notice waiting for you in the bell.

Meeting cancelled and Meeting moved notices work the same way, and the cancellation additionally carries a calendar cancellation so the meeting comes off your own calendar — see what the board hears when a meeting is cancelled or moved.

What happens when the chair starts a meeting?

When whoever is running the meeting chooses Start meeting in Run mode, everyone the meeting is for — the whole board, or just the committee for a committee meeting — gets a Meeting started notice titled "Meeting has started", in the bell and (unless you've turned the Meetings topic's Email box off) by email. The person who pressed Start meeting isn't told, and neither is anyone who answered No to the meeting's RSVP.

If the meeting has a video link, the email's main button is Join the call, which opens the video link directly, with an Open the meeting link beside it. Without a video link the email has a single Open the meeting button. The bell notice always opens the meeting's page.

It's sent once per meeting: pressing Start meeting again, or a second person starting it on another device, never sends it twice.

What a task-assigned notice looks like

The moment a task lands on you — created with you as the owner, handed to you later, or captured from a meeting's action items — you get a Task assigned notice: an item in your bell and, unless you've turned the Tasks topic's Email box off, a branded email with a button straight to the task. Where the work came from a meeting's minutes, the email carries a second button back to those minutes.

This notice does not need a due date — an undated action item announces itself just the same, which is exactly the case a due-date reminder can never cover. You're never notified about a task you assigned to yourself, the previous owner of a reassigned task isn't told they were taken off it, and several tasks handed to you in one go arrive as a single message naming them rather than one message each.

What a due-date-changed notice looks like

When someone else moves the due date of a task assigned to you — earlier, later, newly set, or cleared — you get a Due date changed notice titled with the new date ("Circulate the audit RFP is now due Oct 12, 2026", or "… no longer has a due date"), plus the matching email unless you've turned the Tasks topic's Email box off. The message gives the old and new dates and how far away the new one is, counted from today in your board's time zone, and says plainly when the date moved earlier. Open the task takes you straight to it.

You're not told when you move the date yourself, when the task is already done or cancelled, or when the same change also hands the task to you — the Task assigned notice covers that. Several dates moved in one bulk change arrive as one message. See what happens when I move a task's due date?

What a task-completed notice looks like

When someone marks Done a task you created — on the Tasks page, or by converting a meeting's action items — you get a Task completed notice ("Dana Lee marked "Send bylaws draft to counsel" done") linking straight to the task, plus the matching email unless you've turned the Tasks topic's Email box off. You're not told when you complete it yourself, or when you were also the task's owner, and re-saving an already-done task sends nothing. See who hears when I finish a task?

What document-review notices look like

A review of a draft document — amended bylaws, a new policy — can send you six kinds of notice over its life, all governed by the Documents topic:

• Document out for review when the draft is circulated ("Please comment on "Bylaws""), with the date comments are due.
• New draft for review when a revised draft replaces the one out for comment ("A new draft of "Bylaws" is up for comment — v2"), again with the comment due date if there is one — so you re-read the right text before the deadline.
• Comments due soon two days before the comment deadline and again on the day it's due, at 8:00 AM in your board's time zone — only if you haven't commented yet and the review is still open for comment.
• Comment deadline changed when whoever runs the review moves the comments-due date, with the new date first and the old one after it, both in your board's time zone: "Comments now due Fri, Oct 9, 2026, 5:00 PM EDT — was Tue, Oct 6, 2026, 5:00 PM EDT". If the date was brought forward, the title says Deadline moved earlier and the notice tells you there's less time; if the deadline was removed, it says the review stays open until the board decides. Saving the same date again sends nothing.
• Review comment reply when someone replies to a comment you wrote, or in a thread you've already replied in. It previews the reply and opens the review at that thread. However many replies land, you get one unread notice per thread — once you've read it, the next reply tells you again.
• Review closed when the round ends, with the outcome at the start of the title so you see it even in the bell's one-line view: "Adopted: "Bylaws"" (with the effective date, when one is set), "Not adopted: "Bylaws"", or "Review withdrawn: "Bylaws"".

Each one links straight to the review. You're never told about your own action, and a review that has been decided or withdrawn sends no deadline or reply notices. See who is told, and when.

What availability-poll notices look like

Availability polls put three kinds of notice in your bell. All three belong to the Meetings topic:

• Availability requested: sent when a poll you're invited to is created. It opens the poll in the app, where you can answer under Give your availability without the emailed link.
• Poll scheduled: sent when the poll becomes a meeting, whether an organizer promoted a time or the poll scheduled itself. It links to the meeting.
• Poll needs a decision: sent only to the poll's organizer when the response deadline passes without enough answers to schedule automatically. It links to the poll summary so the organizer can pick a time, extend the deadline, or close the poll.

These notices come in addition to the poll's own emails, never instead of them. Turning off Meetings email stops the emails, but the bell notices still arrive. Turning off Meetings in-app stops the bell notices. See availability polls.

What happens when someone @mentions me in a discussion?

When someone types @ and picks your name in a discussion post, you get a Mentioned you notice in your bell — "Ada Lovelace mentioned you in "Q3 budget"" — and an email that opens with the same line. Both link straight to that post in the thread.

A mention reaches you even if you've muted that space or chosen its daily digest: those per-space settings only thin out the ordinary "new post" email, and a question addressed to you isn't ordinary. It still follows the Discussions row of the preferences grid, though — turn off its Email box and mentions stop emailing you; turn off In-app and they stop reaching your bell.

You get one notice per post, never two: a post that mentions you sends the Mentioned you notice instead of New discussion post. If the author edits a post to add your name, you're told then; an edit that leaves an existing mention in place sends nothing new. Mentioning yourself, or someone outside the space, notifies nobody. Opening the thread clears the notice with the rest of the thread's unread posts. See mentioning someone in a post.

What happens when I'm named a project's owner?

When someone creates a project with you as its owner, or changes an existing project's owner to you, you get a Project owner notice in your bell and, unless you've turned the Tasks topic's Email box off, a matching email — "You're now the owner of Bylaws Revision 2026" — with an Open the project button. It tells you the project's target date, if one is set, and how many open tasks it has.

You're told once per hand-over. Saving the project again with you still as owner sends nothing, and neither does making yourself the owner, clearing the owner, or editing other fields. If the project moves to someone else, only the new owner is told. See projects.

What happens when I'm named a presenter?

When the chair or secretary names you as the presenter of an agenda item, you get a You're presenting notice in your bell and, unless you've turned the Meetings topic's Email box off, a matching email with a View the agenda button. It names the meeting with its date and time (in the meeting's own time zone), the item's number and title, and how long it has on the agenda — for example, "You've been named the presenter of item 3, "Treasurer's report", at October board meeting on Oct 6, 2026, 6:00 PM EDT. It has 10 minutes on the agenda."

You're told once, when you're first named. Saving the item again with you still as presenter sends nothing, and neither does naming yourself or clearing the presenter. If an item is handed to someone else, only the new presenter is told. Only meetings that are still scheduled send these — never a cancelled or completed one. The meeting's Details page also shows you a You're presenting line listing every item you present. See building the agenda.

What a survey-response-requested notice looks like

The moment a survey or board self-assessment is distributed, every member of its audience gets a Survey response requested notice: an item in your bell and, unless you've turned the Surveys topic's Email box off, a branded email — both pointing to the survey's respond page, right in the app. This is separate from the survey's own personal, single-use email link (see Surveys), which is never gated by this preference: it's a direct ask for your answer, not a digest. The notice disappears from the Overview page's Surveys awaiting your response section, and from your Surveys list, the moment you respond, the survey closes, or its deadline passes.

If the survey has a deadline and you still haven't responded, you also get a Survey due soon reminder two days before it and another on the day it's due, both at 8:00 AM in your board's time zone and both stating the deadline with its weekday. They stop the moment you respond or the survey closes, and you won't get one within 24 hours of an administrator's own Send a reminder. They follow the Surveys topic too. See automatic deadline reminders.

What a task reminder looks like

If a task is assigned to you and carries a due date, you get a Task due soon notice when it comes due and, if it's still open, a second one once it's overdue — both governed by the Tasks topic above. A task with no due date, no assignee, or one that's already marked Done or Cancelled never generates a reminder. Each reminder arrives the same way as any other notice: an item in your bell, and — unless you've turned the Tasks topic's Email box off — a branded email linking straight to the task.

What happens when a new governing document is added?

When a document is uploaded as a governing document (bylaws, policies), or an existing document is moved into Governing documents, every currently-serving member who hasn't acknowledged it gets a Please acknowledge notice titled "Please read and acknowledge: document title". It's in your bell and — unless you've turned the Documents topic's Email box off — in your inbox, with a Read and acknowledge button that opens the document, where an Acknowledge button in the Your acknowledgment panel records your sign-off. The person who added or moved the document isn't told. It's sent once per document: moving a document out of Governing documents sends nothing, and moving it back in never sends it to anyone twice. See being asked to acknowledge a new governing document.

What an acknowledgment reminder looks like

If a governing document (bylaws, policies) is waiting on your acknowledgment, an administrator can send you an Acknowledgment reminder from that document's page — see chasing outstanding acknowledgments. It's a direct ask, not a subscription: unlike every other kind of notice, it doesn't have a row in the preferences grid above, so it always reaches your bell. Its companion email still follows your own email opt-in. Once you acknowledge the document, you're no longer a candidate for another reminder about it.

What a note-reply notice looks like

Left a note on a shared page of a board packet? If someone replies to it, you get a Note reply notice linking straight back to that page of the packet with the thread in view — and so does everyone else who has already replied in that thread, except whoever just posted. A private note (one only you can see) never generates a reply notice, because no one else can see or reply to it. A burst of replies in quick succession collapses into a single notice per person rather than one per reply. This is an in-app notice only — there's no accompanying email — and you can turn it off entirely with the Packet note replies row of the preferences grid above.

Good governance tip: if you're the kind of board member who lives in their inbox rather than logging in daily, keep Email switched on for the topics that matter — it's the difference between catching a schedule change today versus a week from now. If your inbox is already full, trim the topics you don't act on rather than turning everything off.