tauri-syntax-permissions

Define explicit permission structures in src-tauri/permissions and reference them from capability files in src-tauri/capabilities to securely configure Tauri 2 capabilities. This transition replaces v1 allowlists with explicit scopes and sets.

Tauri v1 allowlists are replaced by v2 capabilities, which enforce explicit permission definitions using TOML or JSON files. Capabilities require documenting and validating scopes, sets, and platform-specific rules in src-tauri/capabilities.

Migrate allowlist entries to Tauri 2 capability files by creating definitions in src-tauri/capabilities that map previous permissions to explicit scopes and sets. This ensures secure, explicit permission management for desktop apps.

Define custom app permissions in Tauri 2 by creating permission TOML or JSON structures in the src-tauri/permissions directory. Reference these definitions from your capability files to apply a secure baseline.

Tauri 2 permission scope build errors often occur when capability files in src-tauri/capabilities contain invalid references or misconfigured platform-specific rules. Auditing explicit permission definitions helps validate and debug these runtime errors.

Yes, you can apply platform-specific rules in Tauri capability files by configuring explicit permission definitions within src-tauri/capabilities. This allows validating and guiding the creation of targeted scopes and sets for different desktop platforms.