Understanding Notification Types And Requirements

Summary

Users can manage notifications in the Notifications Center. Below is a breakdown of the types of notifications your users might receive and the requirements to enable them: Email, In-app, and SNS notifications.

Feature & User Preferences Availability

  • Batched Notifications & Portal Defaults: Available to all portals as of October 19, 2026.

  • User Preferences: Rolling out gradually to all customers between October 26 and November 10, 2026. If you require early access before your scheduled rollout date, please contact your Customer Success Manager (CSM).

  • You can set your Portal Defaults ahead of the User Preferences release. Your default settings will take effect only once User Preferences are enabled in your portal.

Alongside this update, several notifications gain a new channel (marked (NEW!) in the tables below). Legacy notifications that have not moved to the new Notification Center experience continue to use original email templates with standard Inbox functionality.

Who?

  • Global Availability: Enabled for all users across active portals.

  • Administrative Rights: Administrators with the Manage portal settings permission can configure global portal defaults. Specific notification categories may require your CSM to enable them initially before admin settings take effect.

Don't yet have Bynder? Start Here!

Why?

There are three types of notifications available in your portal: Email, In-app, and SNS. Notifications are an excellent way for users to be aware of their portal happenings. Below is a breakdown of notification types and their specific requirements.

How?

How Batched Notifications Work

Batched Notifications are automatically enabled across all delivery channels for supported high-volume notifications. When rapid, automated batch actions occur (such as archiving thousands of assets or Waiting Room requests), Bynder pauses briefly to collect these events and delivers a single, summarized alert rather than individual notifications for every item.

Setting Portal Notification Defaults (Admins)

Administrators with the Manage portal settings permission can define default delivery channels to manage communication volume and establish a functional baseline. You can set your Portal Defaults ahead of the User Preferences release. Your default settings will take effect only once User Preferences are enabled in your portal.

  1. Navigate to Portal Settings > Notification settings (under Notifications > Defaults).

  2. Locate the notification category and specific notification type you wish to adjust.

  3. Toggle the In-app or Email options to establish your portal baseline.

  4. Click Save and apply, then confirm the prompt in the pop-up modal.

  5. To revert your settings to Bynder's standard behavior, click the Return to default button.

Rules & Precedence

  • Hierarchy: User Preference > Portal Default > Bynder Default.

  • Scope: Portal defaults apply only to users who have never configured personal preferences. Once a user sets a personal preference, it takes precedence and is preserved even if an administrator updates the portal defaults later.

  • Targeting: Portal defaults are applied globally across the entire portal. Per-group, per-role, or per-user default targeting is not supported.

 

Global Notification Availability 

We updated our system to standardize notifications across all portals. Depending on your previous portal configuration, some notifications (such as asset archiving, new version uploads, and Waiting Room requests) may appear as new to you even though they existed previously.

 

Category Notification In-app Email Recipients Can turn off all channels? Notes / Requirements
Asset Bank Asset has been archived Default: ON Default: ON (NEW!) Users who have downloaded the asset before NO, MIN. 1 REQUIRED Supports Batched Notifications
Asset Bank Asset will be archived soon Default: ON Default: OFF (NEW!) Users who have downloaded the asset before Yes

Requires additional setting to be enabled, contact your CSM.

Supports Batched Notifications
Asset Bank Asset has been deleted Default: ON Default: ON (NEW!) Users who have downloaded or shared the asset before Yes Supports Batched Notifications
Asset Bank A new version was uploaded Default: ON Default: ON (NEW!) Users who downloaded the asset before Yes Supports Batched Notifications
Asset Bank Saved filter shared with you   Default: ON Users added as recipients on a saved filter NO, MIN. 1 REQUIRED  
Collections Collection or asset shared with you Default: ON (NEW!) Default: ON Users the collection is shared with NO, MIN. 1 REQUIRED  
Bynder Express Files have been shared Default: ON (NEW!) Default: ON Person who shared the files Yes  
Bynder Express Files have been downloaded Default: ON (NEW!) Default: ON (NEW!) Person who shared the files Yes Supports Batched Notifications
Bynder Express Files shared with you Default: ON (NEW!) Default: ON Recipient of the files NO, MIN. 1 REQUIRED  
Change History Change history export ready Default: ON   User who requested the CSV export NO, MIN. 1 REQUIRED Requires additional setting to be enabled, contact your CSM.
Support Support request received   Default: ON Admin(s) responsible for the relevant support category NO, MIN. 1 REQUIRED Requires support form to be enabled.
User Access Requests A new access request Default: ON (NEW!) Default: ON The approver listed on the registration form Yes  
User Access Requests Access request sent   Default: ON Person who requested access Not Adjustable  
User Access Requests Access request approved   Default: ON Person who requested access Not Adjustable  
User Access Requests Access request rejected   Default: ON Person who requested access Not Adjustable  
User Access Requests Access request for an existing user   Default: ON Person who requested access Yes Sent when the email used to request access already belongs to an existing user.
User Management Invitation received   Default: ON The user the account was created for Not Adjustable Requires the "Send email notification" option to be enabled when creating the user.
User Management Password reset   Default: ON Account owner NO, MIN. 1 REQUIRED  
User Management Account deleted from portal   Default: ON The user whose account was removed Not Adjustable  
User Management Account data deleted   Default: ON The user whose account data was deleted Not Adjustable Sent for GDPR-related account data deletion. Follows the same channel logic as Account deleted from portal.
Studio Design approval requested   Default: ON The approver of the design NO, MIN. 1 REQUIRED  
Studio Design changes requested   Default: ON The designer/contributor(s) of the design NO, MIN. 1 REQUIRED  
Studio Design approved or rejected   Default: ON Person who requested approval NO, MIN. 1 REQUIRED  
External Uploader Files have been uploaded Default: ON (NEW!) Default: ON User who shared files via the External Uploader Yes  
External Uploader Files are ready for download Default: ON Default: ON Email addresses mentioned while uploading files NO, MIN. 1 REQUIRED  
Waiting Room Request has been audited Default: ON Default: ON (NEW!) User who created the Waiting Room request NO, MIN. 1 REQUIRED Supports Batched Notifications
Waiting Room A new upload request Default: ON Default: ON Users who have the Audit uploaded media for this option right set on the metaproperty option level. Users who have the Audit media in the waiting room enabled for their permission profile Yes Supports Batched Notifications
Waiting Room A new download request Default: ON Default: ON Users who have the Audit download requests for this option right set on the metaproperty option level. Users who have the Audit media in the waiting room enabled for their permission profile Yes Supports Batched Notifications

Asset Workflow Notifications 

The notifications in the Asset Workflow table are below. They keep using the original email templates and have limited functionality in the Inbox as they cannot be marked as unread.

Category Notification Recipients Notes / Requirements
Asset Workflow New job creation The user(s) responsible for the first stage  
Asset Workflow Job submitted to the next stage The accountable(s) of the job, the responsible user(s) of the current stage, the responsible user(s) of the stage the job is submitted to  
Asset Workflow Job submitted to the previous stage The accountable(s) of the job, the responsible user(s) of the current stage, the responsible user(s) of the previous stage of the job is submitted to  
Asset Workflow Task completed The creator of the task, the responsible user(s) of the task Sent to responsible user(s) only if someone other than the assigned user completes the task.
Asset Workflow Task responsible assigned The responsible user(s) of the task  
Asset Workflow Task responsible changed The old responsible user(s) of the stage, the new responsible user(s) of the stage, the accountable for the job  
Asset Workflow Stage user invite The invited user The Choose responsible and Allow user invite options must be enabled in the preset the job is based on.
Asset Workflow New message (on an old asset) The owner(s) of the asset and its versions Applies when a message is added directly to an asset rather than a workflow job.
Asset Workflow Workflow completion The accountable(s) of the job, the responsible user(s) of the final stage  
Asset Workflow New comment The accountable(s) of the job, the responsible user(s) of the active stage  
Asset Workflow New comment with user tag The accountable(s) of the job, the responsible user(s) of the active stage, the user who is tagged in the comment  
Asset Workflow Reply to message The user(s) participating in the message thread  
Asset Workflow New private message The user(s) the private message is intended for  
Asset Workflow Reply to private message The user(s) participating in the private message thread.  
Asset Workflow External server removal   An external mailing server needs to be configured.

SNS Notifications

Category Notification Recipients Requirements
Asset Bank New asset upload (None specified) Requires new asset notification and SNS notifications
Asset Bank The new version was uploaded to an existing asset Users who downloaded the asset before Requires new version update notification and SNS notifications
Asset Bank The asset has been archived Users who have downloaded the asset before Requires archive asset notification and SNS notifications
Asset Bank Asset removal Users who have downloaded or shared the asset before Requires removal of asset notification and SNS notifications
Asset Workflow New job creation The user(s) responsible for the first stage (None specified)
Asset Workflow External server removal (None specified) An external mailing server needs to be configured. Requires SNS notifications.

 

Related Articles

How To Configure Webhook Notifications(SNS)

Understanding Bynder's Notification Center And Email Notifications

How To Create And Manage General Notifications

Level: Beginner

Beginner-level articles are for everyone, these articles do not assume any prior Bynder knowledge. These articles are a great place to start your Bynder Journey.

 

Updated