How to Control Snap App Permissions with Real-Time Prompts on Ubuntu

Introduction

If you've been using Ubuntu and noticed a new, unobtrusive prompt asking you to allow or deny an app's access to your camera, microphone, or files—you're experiencing a major upgrade to the system's permission model. Canonical has refined the snap permission system to present these requests at the exact moment an app needs them, similar to what you see on Android or iOS. This guide will walk you through everything you need to know about managing these real-time prompts, from understanding when they appear to adjusting permissions after the fact.

How to Control Snap App Permissions with Real-Time Prompts on Ubuntu — Source: www.omgubuntu.co.uk

What You Need

Ubuntu 24.04 LTS (or a later version that includes the updated permission prompt system)
Snap packages installed — the feature works specifically with snap-based applications
An active internet connection for initial snap updates (if you're updating from an older release)
Basic familiarity with the Ubuntu desktop (you'll need to click prompts and navigate settings)

Step-by-Step Instructions

Step 1: Verify Your Ubuntu Version and Snap Support

Before you can take advantage of runtime permission prompts, make sure your system is up to date. Open a terminal and run:

lsb_release -a

Look for a version number of 24.04 or higher. If you're on an older release, upgrade via Software Updater. Then check that your snap daemon is current:

snap version

You should see snapd version 2.60 or later for full prompt support.

Step 2: Install a Snap App That Requests Permissions

Not all snap apps use runtime prompts—some still rely on static permissions set at install time. The best way to see the feature in action is to install an app that explicitly requests hardware access, such as a camera or file manager. For example:

snap install obsidian --classic

Note: The --classic flag bypasses strict confinement; for testing permission prompts, use confined snaps like gnome-calculator (doesn't need special permissions) or install a media app like vlc from the Snap Store.

Step 3: Trigger a Permission Request

Launch the installed snap application. The first time it attempts to access a protected resource (e.g., camera, microphone, home directory files), a system modal will appear. This is the brain of the new permission system—it asks you to explicitly allow or deny the action. The prompt looks like this:

“Allow to access the camera?” with buttons for Allow, Deny, or Only while the app is open (if applicable).

Step 4: Choose a Permission Response

Your options are straightforward:

Allow — Grants permanent access until you manually revoke it.
Deny — Blocks access forever (within that app), though you can change this later.
Only while the app is open — A temporary grant that expires when the app closes.

Pick the level of trust that matches your use case. For one-time tasks like a video call, the temporary option is safest.

Step 5: Review and Modify Existing Permissions (Post-Prompt)

Changed your mind? You can adjust permissions at any time via the Settings app. Go to Settings > Privacy & Security > App Permissions. Here you’ll see a list of snap apps that have requested access. Click on any app to:

Revoke a previously allowed permission
Grant a permission that was earlier denied
Switch a permanent grant to a temporary one (where the system supports it)

This interface effectively acts as a permission manager, similar to what you’d find on a phone.

Step 6: Understand the Difference from Traditional Permission Models

Before this update, snap apps often requested all permissions at install time—a binary “allow all” or “don’t install.” The new runtime prompts give you granular control after installation. This means you can install a photo editor without worrying it will secretly access your files; it can only do so when you approve the action in real time.

Step 7: Keep Your System Updated for Future Improvements

Canonical continues to refine this feature. To get the latest prompt enhancements and bug fixes, ensure automatic updates are enabled in Software & Updates. You can also manually check for snap updates:

sudo snap refresh

This will pull in any updated permission interfaces from Canonical.

Tips and Best Practices

Deny by default — If you're unsure about an app's need for a resource, select “Deny” or “Only while the app is open.” You can always change it later via Settings.
Monitor permission requests — Frequent prompts from a single app might indicate a bug or overly aggressive resource polling. Consider that a red flag.
Use temporary grants for sensitive hardware — For webcams and microphones, the “Only while the app is open” option minimizes long-term exposure.
Check for classic snaps — Snaps installed with --classic bypass the permission system entirely; they have full system access. Only use classic snaps from trusted sources.
Give feedback — If a permission prompt seems missing or confusing, report it to the snap developer or Canonical via Launchpad. This helps improve the ecosystem.

By following these steps and tips, you can confidently manage application permissions on Ubuntu, enjoying a level of control that previously required third-party tools. The new runtime prompts put you in charge—easily, clearly, and without the bloat of old permission models.

Tags: