Workspace defaults

Admins set what members receive by default, and where Slack messages are posted, under Settings > Workspace > Notifications. The page has three tabs: Notifications, Digest, and Slack channels.

Note

Defaults apply to members who haven’t customized a setting themselves. A member who has changed a row on their own preferences page keeps their choice; changing the default won’t move it. They can return to the default at any time with Use workspace default.

Notifications tab

A matrix of every notification type against the Admin and Member roles, with an Email and a Slack toggle in each cell. Rows are grouped by category and carry the same descriptions members see.

Setting a toggle here changes what a member of that role receives if they haven’t set that row themselves.

This tab also holds the Slack connector selector, which decides the connected Slack workspace used to match members to their Slack accounts. Direct messages aren’t delivered until a connector is selected — see the Slack integration for the full setup.

Digest tab

The same matrix shape, per role:

• Digest enabled — whether members of the role get the digest by default.
• Frequency — Daily, Weekly, or Monthly.
• Sections — which sections the digest includes. Only sections for modules your workspace has enabled are listed.

Frequency and sections are disabled while the digest is off for that role.

For what the digest contains, see Digest emails.

Slack channels tab

Controls where Slack messages are posted.

Workspace default sets the channel that receives notifications when nothing more specific is configured. Both public and private channels are supported; private channels appear in the selector only after you add the Oneleet app to the channel in Slack.

Caution

Notifications can include sensitive data such as vulnerability alerts and PII. Oneleet recommends a private channel with access limited to authorized users.

All notifications lists every notification type with its own routing. Each row takes one of three values:

• Use workspace default — post to the workspace default channel.
• Do not send to Slack — don’t post this notification to any channel.
• A specific channel — post this notification type there instead.

Routing a notification to a dedicated channel is useful when one team owns a class of alert — for example sending code security findings to your engineering channel while everything else goes to the default.

If no workspace default channel is set and a notification has no channel of its own, it isn’t posted to Slack.

Note

These settings govern channel posts only. Slack direct messages follow each member’s own Slack toggle, so Do not send to Slack for a notification type stops the channel post but not the DMs.

Turning notifications off for a member

To stop all notifications for one person — a service account, or someone on extended leave — open the Members page, then the row action menu, and choose Disable notifications. This overrides both their preferences and the workspace defaults. Notifications that always send, such as invitations, are unaffected.