1209551
📖 Tutorial

Mastering App Permissions in Ubuntu: A Step-by-Step Guide to Snap’s New Prompting System

Last updated: 2026-05-08 12:03:53 Intermediate
Complete guide
Follow along with this comprehensive guide

Introduction

If you’ve been using Ubuntu and haven’t explored the latest improvements to its app permission prompts, now is the perfect time. Canonical has revamped the Snap-based permission system, moving from retroactive approval to runtime prompts that appear when an app actually needs access to system resources (like your camera, microphone, or files). This change puts you in control, letting you grant or deny permissions in the moment — similar to how Android and iOS handle it. In this guide, we’ll walk you through the new system, show you how to respond to prompts, manage permissions after the fact, and share tips to stay secure.

Mastering App Permissions in Ubuntu: A Step-by-Step Guide to Snap’s New Prompting System
Source: www.omgubuntu.co.uk

What You Need

  • Ubuntu 22.04 or later (or any recent LTS version with Snap support)
  • The latest version of snapd – run sudo snap refresh snapd in a terminal to ensure you have the updated permission prompting system
  • At least one Snap application that requests hardware or system access (e.g., a camera app, a note-taking tool that wants file access)
  • An active internet connection for downloading apps (if needed)

Step-by-Step Instructions

Step 1: Install a Snap App That Uses Permissions

To experience the new prompts, you need a Snap application that actually requires system access. For example, the GNOME Boxes snap might request camera permissions, or a screenshot tool like Flameshot may ask for screen capture. Install one via the Ubuntu Software Center or using the terminal:

sudo snap install flameshot

After installation, note that the app hasn’t yet been given any permissions – the new system will ask when it first needs them.

Step 2: Launch the App and Trigger a Permission Request

Open your newly installed Snap app from the Applications menu. When the app tries to access a protected resource for the first time (like your webcam or microphone), a modal window will appear on screen. This is the runtime permission prompt, designed to look similar to mobile OS prompts. It will say something like: “Allow [App Name] to access the camera?” with three options:

  • Allow – grants permanent access
  • Deny – blocks access this time and permanently (unless you change later)
  • Only While Using the App – grants temporary access for the current session

Step 3: Choose Your Permission Preference

Read the prompt carefully. If you’re unsure, “Only While Using the App” is the most secure choice for sensitive resources like cameras or location. It revokes permission as soon as you close the app. For less sensitive resources (like file access), you might choose “Allow” to avoid repeated prompts. Click your choice and the app will proceed accordingly. If you deny, the app will either handle it gracefully or show an error.

Step 4: Review and Manage Permissions Later

What if you denied a permission and later change your mind? No problem. Open a terminal and use the snap connections command to list all permissions for a given snap:

snap connections <snap-name>

This shows each interface (like camera or home) and its current status (attached = allowed, detached = denied). To grant a previously denied permission, use:

sudo snap connect <snap-name>:camera :camera

Replace camera with the appropriate interface name. You can also use snap disconnect to revoke a permission that was accidentally allowed.

Mastering App Permissions in Ubuntu: A Step-by-Step Guide to Snap’s New Prompting System
Source: www.omgubuntu.co.uk

Step 5: Understand What Has Changed from Previous Versions

Earlier releases of Ubuntu’s Snap system only allowed you to approve permissions after an app was installed via snap connect commands. The new runtime prompting is a significant upgrade because:

  • Prompts happen in real time when the feature is actually used
  • You can grant temporary access (Only While Using)
  • The system is more like mobile apps, which are familiar to many users
  • It reduces the ‘blanket permission’ problem – you no longer have to pre-approve access before even using the app

This improvement, shared by Canonical engineer Oliver Calder, aims to “empower users” by putting control in their hands at the moment of need.

Step 6: Keep Your System Updated for Best Security

Canonical continues to refine the permission prompting system. To get the latest features and security fixes, regularly update snapd and your installed Snaps:

sudo snap refresh

Always install Snaps from trusted publishers (the Snap Store verifies them). The runtime prompt system only works with interfaces that support it; older snaps may need updates.

Tips for a Secure and Smooth Experience

  • Be skeptical of prompts you didn’t expect. If an app asks for camera access and you’re not using it, deny and check if the app is malicious.
  • Use “Only While Using” for sensitive permissions like microphone, camera, or location. This minimizes exposure.
  • Regularly audit your snap connections with snap connections to see which apps have permissions. Revoke any you no longer need.
  • If you’re a developer, test your snap’s permission requests with the new interface to ensure they trigger prompts correctly. See Snapcraft documentation.
  • Remember that granting “Allow” is permanent until you manually disconnect. Temporary access is safer for one-off uses.
  • Use the GUI tool if you prefer a visual interface: some Ubuntu flavors include a “Permissions” settings panel for Snaps. Check your system settings.

By following these steps, you can take full advantage of Ubuntu’s improved app permission prompting, giving you fine-grained control over what your Snaps can access. The shift to runtime prompts makes desktop security feel as intuitive as on mobile, without sacrificing the power of Linux.