Your single prioritized scroll of everything you have to do — tasks and follow-ups grouped by Overdue, Today, Upcoming, and Anytime, with one-tap complete, snooze, and reschedule.
What My Work Is
A calm, prioritized list of the work that is actually yours to do.
Open My Work from the left sidebar. It is a single scroll of every open task and follow-up assigned to you (or created by you), grouped into four time-based sections so you always know what needs attention first. It replaces the old multi-view, multi-toggle queue with one quiet list. The header reads "My Work" followed by the line "Everything you committed to do, drive it to zero." and a link across to Notifications for the things that are only yours to know.
My Work vs. Notifications
My Work = things you DO— you complete them (capturing what happened), snooze them, or reschedule them. Notifications = things that HAPPENED— you read or archive them. If you ever wonder where something belongs: if there's an action only you can take, it lives in My Work; if it's just an event to be aware of, it lives in the Notifications inbox.
The lanes above your list
Needs you, Needs linking, and Shared work sit above the date sections, and clear themselves as you act.
Above the four date sections, My Work surfaces short lanes of work that arrived on its own rather than being written down by you. A lane appears only when it has something in it, so an empty lane never takes up a line, and a row leaves its lane as soon as you deal with it. Needs you and Needs linking can each be switched off in My Work preferences; Shared workhas no toggle, because an obligation the whole team shares should not sit behind one person's setting.
Needs you · action required. Alerts that need a decision, an answer, or a fix from you, lifted out of the Notifications bell so they cannot scroll away.
Needs linking · unfiled recordings. Meeting recordings the CRM could not match to a record on its own, waiting for you to file them.
Shared work · first to act clears it for everyone. Obligations nobody is individually assigned, such as a duplicate pair the CRM detected or a payment that failed. Each row leads to where the obligation lives, and adds I've got this (which marks the row Claimed by you so your team can see you have it, and leaves it in the lane) and Mark done (which clears it for everyone).
A lane that could not load says so
The one lane that loads on its own is Needs you, and what a failure looks like depends on what is already on screen. With nothing loaded yet, the lane does not stay silent and it does not read as empty: it shows a single line, "Couldn't load Needs you.", with a Retrybutton next to it. With rows already showing, a failed refresh keeps them and says nothing — rows you have are still worth acting on, and the lane refills on its next poll. If the rest of your queue is empty as well, the lane is not drawn at all and the empty-state card carries the disclosure instead.
The queue itself has two failure states
The other two lanes ride the main queue request. With nothing cached, a failure replaces the list with "Couldn't load your work queue." and its own Retry. With rows already loaded, the rows stay exactly where they are and a single muted line appears above them — "Couldn't refresh your work queue. Showing the version that loaded last.", again with a Retry— because a stale row is still actionable and taking three working lanes off screen would cost you more than the stale data does.
In Needs you, each row carries a single primary button, labeled for the job it is: Review, Reply, Answer, Resolve, Approve, Link, Fix, or a plain Open. Clicking it does two things at once: it takes you to where the action actually happens, and it clears the row from the lane, so something you have already handled never sits there waiting a second time. A short line under the title tells you why the row is on your plate now, such as when it was assigned to you or how close its deadline is. On the occasional alert with nowhere to open, the button is left off rather than pointing nowhere. The lane shows a page of rows at most, so once it is full a line underneath reads "More may be waiting. Act on these to see more." It states no number on purpose: a full lane cannot tell how many more there are, so it does not guess one.
Dismiss · a labeled Dismiss button at the end of the row, for something you are not going to act on. It is the same bordered, worded button the Needs linking lane uses, so the same action reads the same way in both lanes. The row clears and a Dismissed confirmation offers Undo for a few seconds.
Dismiss all · in the lane header. It clears the rows currently on screen and counts them in the confirmation ("4 dismissed"), with a single Undo that brings them back. The lane then refills from the server, so anything that was waiting behind those rows appears rather than the lane looking finished.
Save as task · turns the alert into a durable task in your list that deep-links to where the action happens, and files the alert away. It appears only on the alert types that can become a task, and only if your role can create tasks.
Dismissing only affects your copy
Marking one of your own alerts read is personal to you, so dismissing a row here never clears it from a teammate's lane and never cancels the underlying work. It also stays available to view-only members, who see the lane without the Save as task button.
Needs linking lists recordings that finished without a home. Each row shows the file name, which provider it came from and whether it is a recording, a transcript, or a summary, and the date it was Added (when the CRM pulled it in, which is not necessarily the day of the meeting). When a summary is available, a one-line lead tells you what the meeting was about, so you can file it without opening anything. See Recordings & transcripts for the full picture.
The lane loads a page of recordings at a time. When more are waiting than it loaded, a muted line under the header says so with a real count, such as "Showing 20 of 63. Link or dismiss these to see more." When any of the recordings on screen are yours to file, that line also reminds you that dismissing moves a recording to the Archived tab in Recordings, where you can restore it.
Link to · the picker on the row. Switch between People, Companies, and Deals, type at least two characters, and choose the record. The recording files itself onto it and the row clears.
Open recording · the small arrow icon opens the file with the provider in a new tab, for when you need to check what the meeting was before filing it.
Dismiss · for a recording that does not belong on any record. It never deletes anything: the recording moves to the Archived tab in Recordings, where you can restore it, the saved transcript is kept, and a confirmation offers Undo for a few seconds.
Dismiss all · in the lane header, once more than one of the loaded recordings is yours to file. It clears exactly those, so when it cannot reach everything it drops the word "all" and says what it will do instead: Dismiss these 20. One Undo covers the whole batch, and the confirmation names how many are still unfiled behind them. When the batch would clear a recording belonging to someone else, a short confirmation asks first.
Hiding a lane is not the same as clearing it
Switching a lane off in My Work preferences only removes it from this page. Nothing is dropped or silenced: action-required alerts still live in the Notifications bell and inbox, and unfiled recordings still wait on the Recordings page.
Filing a recording follows your Calendar edit permission
Linking and dismissing a recording both change calendar data, so they follow Calendar edit, not merely being able to see the calendar. Without it you still get the lane: an unfiled recording of yours has nowhere else in the app to be nudged from, so your own are listed read-only, each marked View only, with the arrow that opens the file with its provider still there when the provider gave a link. Calendar edit is what adds the Link to picker and Dismiss on the row, and Dismiss all in the header once more than one of the loaded recordings is yours to file. How far the lane reaches past your own recordings is set by the narrower of your two Calendar scopes, view and edit, and only on the Team view: on Mine you only ever see your own. Which of those you can then act on is set out in Recordings & transcripts, including what Team means before you have set up teams.
The Prioritized Scroll
Four collapsible sections, each with a live count visible at a glance.
Instead of switching between bucket tabs, My Work shows all four sections at once in a fixed priority order. Every section header carries a live count, so you can see "3 overdue · 5 today" without clicking anything:
Overdue · anything past its due date. Its count turns red as soon as it is above zero; the badge behind the number stays neutral, so one section reads urgent without the whole row going red.
Today · work due today.
Upcoming · work due later.
Anytime · tasks with no due date.
Click any section header to collapse or expand it. A collapsed header still shows its live count, so a section never hides how much is in it. Your collapse state is remembered for the rest of your browser session, and which sections a fresh visit starts expanded is yours to set in My Work preferences (out of the box, Overdue, Today, and Upcoming open and Anytime starts collapsed). An empty section does not disappear: it shows a thin line such as "Nothing overdue. You're all caught up." so the layout never jumps around.
When there is genuinely nothing left, the whole page shows one calm "You're all caught up." with the line "Nothing needs your attention right now." That is a claim about the whole surface, so the page makes it only when it can stand behind it:
A lane you switched off · if a hidden lane could still be holding work, the page says "Your queue is empty." instead, names what you hid ("Needs you is hidden.", or both lanes when both are off), and offers an Open preferences link that opens the same panel as the header gear. When it can see that the hidden lane is empty anyway, it stays quiet and you get the caught-up state.
A lane that has not answered · a lane that did not answer is not a lane that is clear, so the caught-up wording never appears over one. While a lane is still loading the page simply keeps showing the buckets. Once a lane's request has failed and there is nothing else to show — every bucket at zero and no other lane holding rows — you get "Your queue is empty." plus a line naming what could not be read ("Needs you could not be loaded, so it may be holding work.") and a Retry.
The dot on the My Work item
A small dot means the page has something on it that the number deliberately does not count.
The My Work item in the sidebar, and the My Work tab on mobile, carries a number for the work that is overdue or due today. That number is deliberately narrow: it is the pile you are meant to drive to zero, not a tally of everything the page holds. The side effect is that a day with nothing due would leave the item looking empty while the page still has rows on it. So when the number is zero and there is still something to open, the item carries a small dot instead. The dot states no number on purpose, because it is a presence signal rather than a count, and the number and the dot never appear at the same time.
An unfiled recording of your own · one of your unfiled recordings waiting in the Needs linking lane, including when your role cannot file it. It is always self-scoped: a teammate's unfiled recording never lights your dot, even on the Team view and even with an organization-wide scope.
Shared work · an unresolved row in the Shared work lane, such as a duplicate pair the CRM detected, when it is the kind of obligation your role can act on.
A task with no deadline pressure · one of your own open tasks that has no due date, or is due within the next week. The dot stops where the page stops: Upcoming reaches seven days out, so a task due next month renders in no bucket and lights nothing.
Two things deliberately do not light it. Needs you rows do not, because every one of them is also an unread notification, so the Notifications bell is already carrying a dot for you and a second one would say nothing new. An activity that is undated or due later does not either; the no-deadline check above is tasks only.
Two dots, two meanings
A dot on Notifications means you have something unread there. A dot on My Workmeans the page holds rows the overdue-and-due-today number does not count. They look alike because they say the same kind of thing, "there is something here", but they point at different pages. Screen readers announce this one as "My Work, items waiting".
Completing Work
A clearly labeled Mark done button on every row — with one-tap Undo and an optional outcome capture.
Every row has a clearly labeled Mark done button in its trailing block, right after the due date. It reads as a real button, text plus a check glyph, so there is never any doubt about which control finishes an item. On a narrow screen the word gives way to the check glyph alone to keep the row intact, and the button keeps its Mark donename for screen readers and voice control. Click it once to mark the item done: it shows the check optimistically, the row drops out, and the section count decrements immediately; if the request fails, the change rolls back and a toast lets you retry. The same labeled button appears in the item's peek footer, and the success toast reads "Marked done", so completing always looks and reads the same.
The Mark done button is how you remove something from your list
Marking an item done is the way you take it off My Work — done is "remove from my list." It is terminal but never a trap: every complete carries a one-tap Undo. If you want to get rid of an item without recording it as done, use Deletein the peek (see below) — that is the deliberate, reversible "this should not exist" action, separate from the everyday complete.
One square on the row: the select checkbox
The only checkbox on a row is the leading select checkbox, used purely for picking rows for a bulk action (see Selecting Multiple Items below). Completing lives on the labeled Mark donebutton after the due date instead — so there is no row of look-alike squares to second-guess, and selecting items for a bulk action can never complete one by accident.
Completing never traps you and never loses what happened. The success toast carries a one-tap Undo— so an accidental complete is always reversible — and, for a task or follow-up, an Add outcome action (an activity row is already the record of what happened, so it just gets Undo). Add outcomeopens the activity composer pre-filled with the item's contact and defaulted to a note; switch the type to Call to capture the call result. You record what happened in a couple of taps. From the same panel you can schedule the next follow-up— pre-suggested whenever you log a call, email, meeting, or note, so "always have a next step" is the default and skipping it is the deliberate choice. All of it is optional: ignore the toast and the item is simply done. Logging an outcome no longer lives in the snooze menu — it is part of completing.
Done, Defer, and Update are three different things
These three actions never share a control, so you always know what a tap will do: Done is the labeled Mark donebutton (and a swipe-right on mobile) — it removes the item from your list. Deferis snooze / reschedule — it keeps the item but moves when it is due. Updateis the comment thread in the peek — it adds a note or @mention without changing the item's status or date. Completing is no longer overloaded to also mean "log what happened": outcome capture is offered after you complete, via the Undo toast.
Reassigning a task (managers)
The ··· menu's Reassign(managers only) opens the task's detail panel, where you change the owner directly — the same place every other task field is edited.
Opening an Item In Place (the Peek)
Click anything to slide a fast, calm reader open over the list — no page jump, no lost place.
Clicking the body of any row opens a fast in-page peek— a slide-over panel on the right (a bottom sheet on mobile) that shows the item's details over the still-visible list. The panel opens instantly: the header, status, and schedule appear the moment you click, drawn from the row you already see, and the rest of the details fill in a beat later. You never wait on a blank screen. Skim it, update it, mark it complete, snooze it, or remove it, then close the peek and you are exactly where you left off — same scroll position, same filters. It is the fast way to deal with an item without losing your flow through the rest of the queue.
The peek is a calm reader, not the full editor. It shows only what you need to act: the title and type, status, who created it and when, any notes, the due date, the schedule and reminders, the assignee, links to the related record, and a Comments thread for updates. It deliberately leaves the heavier machinery — subtasks, dependencies, time estimates, attachments — to the full record page, so the quick view stays quick. When you do need everything, the peek's Open full record action takes you to the complete editing page.
Open it — click anywhere on the row body, or press Space (or O / Enter) on the focused row. Every row opens its peek — nothing hard-navigates out of My Work on a click.
Walk the queue — with the peek open, J / K (or ↑ / ↓) move the peek to the previous or next row without closing it.
Close it — press Esc, click the close button, click outside the panel, or use your browser's Back button. Closing returns keyboard focus to the row you opened it from.
Open the full record — the peek has an Open full record action (in the footer and in the ··· menu) for when you need the complete page rather than the quick view.
The peek is shareable and linkable: opening one adds ?peek=task:… (or ?peek=activity:…) to the page URL, so a refresh re-opens the same item and you can paste the link to a teammate. Closing the peek removes only that part of the URL — your scope, filters, and section state are preserved. Pressing Back simply closes the peek rather than leaving the page.
Converted notifications peek too — with the deep link one tap away
A task created from a notification, with Save as task in the Notifications inbox or in the Needs you lane, carries a deep link to where the real action happens (an approval queue, a billing page, an email thread). Clicking the row still opens the peeklike any other — so you can skim and triage it in place — and its Open full record action takes you straight to that surface when you are ready to act. The deep link is never lost; it is simply one tap away rather than a forced jump.
Comments & @Mentions
Add an update to any task or activity, and loop in a teammate with @.
Every item's peek has a Commentsthread — for follow-ups, calls, emails, meetings, and notes as well as tasks. This is how you add an update to a piece of work without changing its status or due date: jot what is happening, leave context for whoever picks it up next, or record a quick decision. You can edit and delete your own comments; each shows its author and a relative timestamp.
Type @in the composer to mention a teammate. A picker of your organization's members appears (a full-width sheet on mobile); choose someone and they are highlighted in the posted comment and notified— the mention shows up in their Notifications bell under the Mentionstab, with a link straight back to this item's peek. You can only mention people in your own organization.
Schedule & Reminders (in the Peek)
Set the due time and Google-Calendar-style offset reminders right from the peek.
The peek's Schedule section lets you set the due date and time, and add reminders that notify you a chosen amount of time beforethe due time — exactly like Google Calendar. Pick an offset from the list (At time of event, 30 minutes before, 1 hour before, 1 day before, 1 week before, or a custom amount), and add up to a few reminders per item. The hint under the editor reads "Notify before the due time". Make your changes and tap Save; the reminder fires from this offset every time, and changing the due date re-arms it automatically.
Offset reminders, not a one-off ping — a reminder is always relative ("30 minutes before"), so it stays correct even if you reschedule the item. The old one-shot "Remind Me" is gone.
Connected to your calendar — if you have a calendar connected, these reminders sync as the calendar event's notifications. With Outlook (Microsoft), the editor offers a single popup reminder; with Google, you can add several (popup or email).
A reminder is not a snooze — a reminder notifies you ahead of an unchanged due time. Snooze (below) is the opposite: it moves the due date. They are deliberately separate.
Needs a due time — the reminders editor is enabled once the item has a due date; with no due date there is nothing to count back from.
Who can edit the schedule
The editable Schedule and Reminders block appears only for an item you can change — one you own, are assigned, or manage, and that isn't already complete. Otherwise the peek shows the schedule as read-only text. Reminders are authored in the peek; the row's ··· menu keeps its snooze presets and does not duplicate the offset-reminder editor.
Delete vs. Done
Two different ways to remove an item — both reversible, used for different reasons.
Done (the labeled Mark donebutton) is the everyday way to clear finished work off your list. But sometimes an item should not exist at all — a duplicate, a mistake, something that turned out to be irrelevant. For that, the peek's ··· menu has a distinct Delete action.
Done — the work happened and is complete. It leaves your list but stays in the record as completed. This is the default and by far the most common action.
Delete — the item should be removed entirely. It is a soft delete: the item is archived, not destroyed, and a one-tap Undo brings it back. Delete is deliberately tucked into the peek menu, not on the row, so it is never an accidental tap.
You can only delete work you're allowed to
Deleting a task or activity respects permissions: you can delete your own work (and managers can delete their team's), but you cannot delete a teammate's item if your role does not allow it — the action is hidden or returns a clear "not allowed" message rather than failing silently.
Snoozing & Deferring
A flat snooze model — at most two levels deep, never a nested submenu.
Each row has a ··· menu that collects every single-row defer action in one flat list (no submenus). On mobile, a swipe-left on the row is the fast path to snooze. The ···menu's presets are:
Tomorrow — Moves the item to tomorrow.
This evening — Sets it to 6:00 PM today. If it is already past 6:00 PM, it falls forward to tomorrow morning instead of landing in the past.
This weekend — Moves it to the upcoming Saturday.
Next week — Moves it to the start of next week.
Pick a date… — Opens a small date picker to choose any future date.
Reassign — Hand the item to a teammate (managers only); opens the task's detail panel to change the owner.
Open full record — Jump to the item's complete page when the peek isn't enough.
Delete — Remove the item entirely (soft delete with Undo) — see Delete vs. Done above.
Snoozing a Today item to This eveningkeeps it in the Today section — it simply re-orders below the rest of today's work rather than jumping to a different bucket.
Selecting Multiple Items
Pick several rows and act on them at once — no persistent bulk button cluttering the list.
The old persistent Reschedule all button is gone. In its place is a Gmail- and Superhuman-style multi-select: pick exactly the rows you want, and a contextual action bar appears with everything you can do to them. Selection is a distinct gesture from completing— the leading checkbox only ever means "select," while completing lives on the labeled Mark done button, so picking items for a bulk action never risks completing them by accident.
Select checkbox — hover a row to reveal a small select checkbox in the leading gutter; click it to add the row to your selection.
Modifier-click — Cmd/Ctrl+click a row toggles it in the selection; Shift+click selects a whole range from the last one you picked.
Keyboard — press X to toggle the focused row, Shift+X (or Shift+↑/↓) to extend the range, and Cmd/Ctrl+A to select every row your filters leave in the queue — including rows inside a collapsed section, up to the 1,000 limit — so check what a bulk verb will reach before you run it. The lanes above the list are not part of a selection, and while your focus is inside one the chord goes back to your browser.
Long-press (mobile) — press and hold a row to enter multi-select mode; a plain tap still opens the peek.
As soon as you select something, a floating action bar appears centered along the bottom of the screen (above the mobile bottom nav and safe area) and stays put while you scroll. It shows "N selected", a small clear (×) control beside the count (or press Esc), a Select all N option whenever the list still holds rows you have not picked, and the bulk verbs:
Mark done — mark every selected item done at once (the bulk "remove from my list"), under the same label the row itself uses.
Reschedule… — pick a date and move all selected tasks to it in one round-trip.
Snooze… — defer the whole selection with the same presets as a single row.
Reassign… — opens the first selected task's detail panel, where you set the owner (managers only).
Delete — remove the selection (soft delete with Undo); de-emphasized so it is never the easy mis-tap.
Mixed selections do the right thing
A selection can mix tasks and activities. Each verb applies to the items it can act on: Reschedule and Reassign are for tasks, so on a mixed selection they move the tasks and leave the rest alone, and they switch off with a short tooltip only when nothing you picked is a task. Changing your scope, bucket, or filters clears the selection automatically, so a bulk action can never hit rows you can no longer see. You can select up to 1,000 items at a time.
Turning a Notification into Work
One button, in two places, connects an alert to your to-do list.
Some notifications are not just events — they require an action only you can take (an approval request, an agent question, an RSVP, a verification step). On those rows in the Notifications inbox, a Save as task button creates a durable task in My Work that deep-links straight to where the real action happens. The same button, with the same label, is offered on the Needs you lane at the top of My Work. The notification is archived once converted, so it stops cluttering your inbox but the work itself can never scroll away. Converting the same notification twice updates the existing task rather than creating a duplicate.
It appears only on the alert types that can become a task, and only for a role that can create tasks. Saving as a task is deliberately a choice, not the default: most rows in the Needs you lane are handled in one click on their primary button, and only the ones you want to keep on your list past today need to become a real task.
Mine vs. Team (Managers)
My Work always defaults to your own work.
My Work defaults to Minefor everyone — the page only ever shows your own work first. Managers and admins also get a Mine | Teamtoggle in the header to switch to the team's queue when they need the wider view; which of the two it opens on is the Default scope you set in My Work preferences, and that is Mine out of the box. Reps and individual contributors see only their own work and have no toggle. Read-only (view-only) users see the team's work as a list with all the complete, snooze, and convert controls hidden.
Filtering
A single '+ Filter' control narrows the list without leaving the page.
A single + Filter control lets you narrow the scroll by Type (Task, Follow-up, Call, and so on) and by whether an item is a follow-up. Managers viewing the Team scope also get an Assigneefilter. Filtering happens instantly over the work already on screen — no extra loading. A Clear filters control appears whenever a filter is active, and a distinct empty state tells you when a filter (rather than an empty queue) is hiding everything.
Keyboard Shortcuts
Move through, open, complete, and select your work without the mouse.
C completes, X selects
The two keys that used to both mean "complete" are now distinct, matching the rest of the app: C always completes the focused item, and X always selects it for a bulk action. They never overlap, so you can triage and multi-select from the keyboard without second-guessing which is which.
Jor↓Focus the next item (or move the open peek to it)
Kor↑Focus the previous item (or move the open peek to it)
SpaceOpen the peek for the focused item
OorEnterOpen the focused item's peek
CMark the focused item complete
XToggle the focused item in your selection
Shift+XorShift+↑↓Extend the selection as a range
Ctrl+A/⌘+ASelect every item in the queue, collapsed sections included (up to 1,000)
HSnooze the focused item using your default snooze preset (Tomorrow out of the box)
EscClear the selection, else close the peek, else close help
GthenNGo to the Notifications inbox
?Show the shortcuts help sheet
Esc works in priority order: if you have rows selected it clears the selection first; otherwise it closes the open peek (returning focus to the row you opened it from); otherwise it closes the help sheet.
Shortcuts pause while typing, and inside the lanes
Keyboard shortcuts are suspended while you are typing in a filter, a comment, or any text field, so @mentioning a teammate never triggers a triage shortcut. They are also suspended while your focus sits inside one of the lanes above the list: those rows are not part of the queue you walk with J and K, so a keystroke there belongs to the lane's own buttons rather than to some row further down the page. The same holds while a menu or a dialog is open over the list, including an open peek: the keys belong to what is in front of you, not to the row behind it, and the one thing that still reaches the queue there is walking the open peek with J and K. Esc is the exception and always gets through. Read-only users see only the non-destructive shortcuts (focus, peek, select, go to notifications, help); the mutating keys (complete, snooze) are hidden. Undoing a complete is not a key: it is the Undo on the confirmation the complete raises.
On Mobile
A first-class touch experience — swipe, sheets, and pull-to-refresh, all in the thumb zone.
My Work is built for one-handed use on a phone, not just shrunk to fit. The swipe verbs are additive rather than the only way in: everything a swipe does also exists as an always-visible control on the row — Mark done and the ···menu — and those controls are what a screen reader reads and activates, so no row action is gesture-only. Pull-to-refresh is the one gesture with no button behind it — reloading the page does the same job.
Swipe right to complete — drag a row right to reveal the Complete action; a longer drag or a quick flick commits it, with a haptic tap. The same Undo applies as the Mark done button.
Swipe left to snooze — drag a row left to snooze it to tomorrow. A short swipe rests on a button; a long swipe commits. Swiping is additive — the Mark done button and ··· menu still work.
Tap to peek — tapping a row opens its details as a bottom sheet with a drag handle. Drag it between a half-height and full-height detent, flick it down to dismiss, tap outside, use the explicit Close button, or press Back.
Long-press to multi-select — press and hold to enter selection mode and bring up the bulk action bar; a plain tap still opens the peek.
Pull to refresh — pull down at the top of the list to refresh your work.
When you focus the comment composer to add an update or @mention a teammate, it lifts above the keyboard and the @mention picker opens as a full-width panel rather than a fiddly floating popover. Primary actions sit in the bottom thumb zone, clear of the home indicator and the bottom navigation, with comfortably large touch targets throughout. If you have reduced-motion turned on, the swipe and sheet animations snap instead of following your finger.
Where Did My Reminders Go?
Task and activity reminders no longer ping the in-app inbox.
Reminders live in My Work now
Task-due-soon and activity reminders no longer appear as in-app notifications. The Overdue and Todaysections of My Work — plus the reminder emails you already receive — cover them. This removes the duplicate ping in your notifications inbox without losing the reminder itself. Manage which reminders email you under Settings → Notifications.
Comments & @Mentions
Add an update to any task or activity, and loop in a teammate with @.