Skip to main content
Workspace defaults set what a person gets before they choose for themselves. Open Settings → Notifications.
A default is a starting point, not a lock. Anyone can change these for themselves from their profile. The one exception is the reminder switches – see below.

​
Why defaults exist

A new person joining Northwind Studio should not have to configure ten switches before they hear about their first assignment. Defaults mean the workspace decides what “normal” looks like, and individuals adjust from there.

​
What is on the page

The page reads “What everyone gets by default. Changes save as you make them.” It holds two cards.

​
What everyone gets

Marked Affects everyone. Described as “The starting point for every member. Anyone can change these for themselves from their profile.” A table with an In-app and an Email switch for each of seven categories: A switch you have never touched shows as on, because “no workspace opinion” falls through to the product default.

​
Workspace defaults for reminders

Also marked Affects everyone. Described as “Applies to anyone who has not set their own times. Everyone gets these times in their own timezone.” Full detail on the three reminder slots is in Reminders.

​
How to change a default

1

Open workspace notification settings

Go to Settings → Notifications.
2

Flip a switch

Each cell saves on its own, the moment you click it. There is no save button.
3

Check the effect

Nothing changes for people who already chose for themselves. Everyone else follows the new default from the next notification onward.
Changing a default does not rewrite anyone’s saved settings. If half your team has already customised theirs, a default change reaches only the other half.

​
Completion watchers

Who hears when tasks are completed or reopened is a named list, not a role query. Pick people with the member picker. The default is Nobody. Anyone on this list is told every time a task is marked complete anywhere in the workspace, and again if it is reopened – on top of whoever the task was assigned to.
A named list is deliberate. A role query silently re-aims itself as people change roles. A list only changes when an admin changes it, which is what you want for something that emails a human on every completion.
Use it sparingly. On a busy workspace this is the loudest setting on the page.

​
Defaults versus reminders – the difference that matters

In plain terms: an admin switching a reminder slot off silences it for everyone, and no individual can turn it back on. An admin switching a channel default off just changes the starting point. The reminder card’s own text tells a member which state they are in – a member whose reminder was killed at workspace level sees “Switched off for the whole workspace” and a disabled switch.

​
Example

Maya Ellis is setting up Northwind Studio for 12 people.
1

Turn the noisy category down

Project changes – she leaves in-app on and switches email off. Twelve people do not each need an email when a project status moves.
2

Keep approvals loud

Approvals – both channels on. A stuck timesheet costs the whole week.
3

Leave security alone

Security – she leaves it as is. Those emails go out regardless.
4

Set reminder times to match the studio

Morning 08:30, evening 17:30, deadline check 2 hours before each person’s day ends.
5

Name a completion watcher

She adds Priya Raman to Who hears when tasks are completed or reopened, so the Project Manager sees delivery flow without opening every project.
Sarah Lin, who starts at 07:00, later sets her own morning reminder to 07:15. That beats the workspace 08:30, because a time is most-specific-wins.

​
Options and settings

​
Permissions

This is the same capability that guards General settings. A member without it who lands here sees a card titled “Looking for your reminders?” and a Go to my profile button. Non-admins looking at the completion watcher control see “Only owners and admins can change this.”

​
What happens next

Each change takes effect on the very next notification. Nothing is queued and nothing is retroactive – notifications already sent are unaffected. Each cell is saved on its own, so two admins editing the page at the same time cannot overwrite each other’s work.

​
Common questions

Only if they have never set that switch themselves. Anyone who has chosen keeps their choice. And they can always turn it back on.
Not from this page. Channel defaults are defaults. If a notification truly must reach people, the reminder switches are the only floor available, and they only cover the three daily reminders.
The workspace page groups notifications into seven categories. Your own page lists ten more specific rows. Both control the same notifications – the workspace view is the coarser one.
Yes. Someone who joins today and never opens their settings follows every default on this page.
Usually nobody, or one delivery lead. Every person you add gets a notification for every completed task in the workspace.
No. Webhook endpoints are configured one at a time under Webhooks.

​
Troubleshooting

A change did not save. An error appears: “Could not change that default.” Nothing else was altered. Click the switch again. People still get emails I switched off. They set that switch themselves, and their choice wins. Ask them, or open their member record and change it with them. Someone says their reminder will not turn on. Check the workspace reminder switch for that slot. A workspace-off reminder cannot be turned on by an individual, and their screen says so.

Your notification settings

What each person controls for themselves.

Reminders

The three daily checks in detail.

Notifications overview

How the notification system fits together.

Notification types

Every notification, its trigger, and its recipients.

Roles and capabilities

Who holds workspace.updateSettings.

Apps and modules

Turning an app off removes its notifications entirely.