NodlumeNodlume
Tauri permissions generator

Tauri notification permission: notification:default

The notification plugin (tauri-plugin-notification) posts OS-level notifications — the toast in Windows' notification centre, the banner on macOS, a desktop notification on Linux — from either the Rust host or the frontend through @tauri-apps/plugin-notification.

notification:default grants the send, permission-check and permission-request commands. The operating system still asks the user the first time an app notifies, so the frontend should call isPermissionGranted and requestPermission before sending rather than assuming the capability grant is the whole story.

Notifications at a glance

Permission
notification:default
Cargo crate
tauri-plugin-notification
npm bindings
@tauri-apps/plugin-notification
Builder call
.plugin(tauri_plugin_notification::init())
What it enables
OS-level notifications.
What it widens
Posts OS notifications. The operating system still prompts the user the first time.

The four files that must agree

Capability file

src-tauri/capabilities/default.json
{
  "$schema": "../gen/schemas/desktop-schema.json",
  "identifier": "default",
  "description": "Capabilities granted to the main window.",
  "windows": [
    "main"
  ],
  "permissions": [
    "core:default",
    "notification:default"
  ]
}

core:default is the baseline every window has; the plugin permission is the one line this page adds.

Cargo dependency

src-tauri/Cargo.toml
[dependencies]
tauri = { version = "2", features = [] }
serde = { version = "1", features = ["derive"] }
serde_json = "1"
tauri-plugin-notification = "2"

Plugin registration

src-tauri/src/lib.rs
#[cfg_attr(mobile, tauri::mobile_entry_point)]
pub fn run() {
    tauri::Builder::default()
        .plugin(tauri_plugin_notification::init())
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

A crate that is declared but never registered is dead weight; one registered without its permission is a runtime denial.

Frontend bindings

terminal
npm install @tauri-apps/plugin-notification

notification:default, answered

The longer version is in the guide Tauri 2 permissions: capabilities without the runtime denials.

What does notification:default grant in Tauri 2?
notification:default is the default permission set of tauri-plugin-notification. It oS-level notifications. Tauri 2 denies every command that is not listed in a capability file, so without this line the plugin's commands fail at runtime even though the crate compiles and is registered.
Why does my notifications call fail with a permission error?
Three files have to agree: tauri-plugin-notification in Cargo.toml, .plugin(tauri_plugin_notification::init()) in src/lib.rs, and notification:default in the capability file under src-tauri/capabilities/. The ACL is checked when a command is invoked, not when the app is built, so a missing permission string compiles cleanly and denies at runtime. The frontend also needs @tauri-apps/plugin-notification installed to call it.
Is notification:default safe to ship?
Posts OS notifications. The operating system still prompts the user the first time. Permissions are additive on top of core:default, so the least-privilege shape is to grant only the plugins the app calls, and to prefer the plugin's granular allow-* permissions over the default set wherever a command or path can be named.

Combine it with the rest of your capability file

The Tauri permissions generator builds the whole file from the same catalogue — tick every plugin the app calls, add a custom title bar's window permissions, and copy the capability JSON, Cargo dependencies, builder chain and npm install line together. In the Nodlume workspace the same selection is what the Desktop export writes into src-tauri.

Open the generator

Other Tauri 2 plugin permissions

We'd like to use Google cookies to understand how Nodlume is used and to measure our advertising. Nothing loads until you choose, and declining does not affect anything in the app.