A Step-by-Step Guide to Managing App Permissions in Ubuntu's New Prompt System
What You Need
- A computer running Ubuntu 24.04 LTS or later (the improved prompting feature debuted in this release).
- An internet connection to install or update Snap packages.
- A Snap application that requests system-level permissions (e.g., camera, microphone, location, or file access).
- Basic familiarity with the Ubuntu desktop environment (clicking buttons, navigating menus).
Introduction
Ubuntu’s app permission prompting has received a major upgrade in the latest release, bringing a mobile-style runtime request system to the desktop. If you’ve been relying on traditional Linux permissions or manually granting blanket access to Snap applications, it’s time to rethink your approach. This guide will walk you through the new feature step by step, showing you how to take control of what your apps can see, hear, and access—without compromising security or usability.

Step 1: Update or Install Ubuntu 24.04+
First, ensure you’re running a version of Ubuntu that includes the enhanced prompting. Open the Software & Updates tool from the system menu, go to the Updates tab, and click Check. If an upgrade to 24.04 LTS or a newer release is available, follow the on-screen instructions to install it. Alternatively, if you’re starting fresh, download the latest ISO and perform a clean installation.
Step 2: Confirm Snap Support Is Active
The new permission prompts are part of the Snap ecosystem. Verify that Snap is enabled by opening a terminal (press Ctrl+Alt+T) and typing:
snap version
You should see version numbers for Snapd and the Snap command. If the command isn’t found, install Snapd with:
sudo apt update && sudo apt install snapd
After installation, log out and back in to ensure the Snap socket is active.
Step 3: Install a Snap App That Requires Permissions
To experience the prompting in action, you need a Snap app that requests hardware or system access. Good examples include video chatting apps (camera and microphone), photo editors (file system), or location services. Use the Ubuntu Software Center or the terminal. For instance, to install the popular video conferencing app Zoom (Snap version):
sudo snap install zoom-client
Once installed, launch it from the application menu.
Step 4: Trigger a Permission Request
Now, perform an action inside the app that would normally require a permission. For Zoom, click New Meeting and then Start Video. A modal window should appear in the center of your screen, similar to what you see on a smartphone:
“Allow Zoom to access your camera?”
You’ll see buttons for Deny, Allow, and, depending on the permission type, Only While Using the App. This last option is a game-changer: it grants temporary access that revokes automatically when you close the app.
Step 5: Choose Your Permission Level
Evaluate the request critically. If you trust the app and need the feature, click Allow. If you’re uncertain or want to test the app’s basic functionality first, pick Deny—the app should degrade gracefully. For permissions like location or microphone, Only While Using the App is often the smartest choice. Once selected, the prompt disappears and the app continues.
Step 6: Review and Revoke Permissions Later
Don’t worry if you regret a choice. Ubuntu stores granted permissions and lets you change them at any time. Open Settings → Privacy & Security → App Permissions. Here, you’ll see a list of categories (Camera, Microphone, Location, etc.). Click one, then toggle permissions for each app on or off. You can also switch from “Allow” to “Only while using the app” from this interface.

Step 7: Verify the Prompt Is Working Correctly
To double-check that the new prompting is active, try launching a second instance of the same app while it’s already running. The prompt should not reappear for a permission already granted in the current session. If you revoke a permission while the app is open, the app won’t be notified immediately—restart the app for the change to take effect.
Step 8: Troubleshoot Common Issues
If you don’t see the permission prompt, ensure:
- The app is installed as a Snap (not a .deb or Flatpak). The new system only applies to Snap packages.
- Your system is fully updated: run
sudo apt update && sudo apt upgradeandsudo snap refresh. - No third-party firewall or security tool is blocking the Snap permission dialogue.
- You’ve given the app an opportunity to request the permission (e.g., clicking the camera icon).
Tips for Getting the Most Out of App Permissions
- Think before you click: Treat each permission request like it’s from a new contact. Just because an app asks for camera access doesn’t mean it needs it—many apps request permissions unnecessarily.
- Use “Only While Using the App” frequently: This option provides the best balance between functionality and privacy. It’s available for time‑sensitive permissions like camera and microphone.
- Review permissions periodically: Go to Settings → App Permissions every few weeks to audit which apps have which rights. Revoke any that seem suspicious or are no longer needed.
- Combine with classic Linux controls: Snap permissions are separate from traditional filesystem permissions (chmod, file ownership). Use both layers for defense in depth.
- Understand the limits: Not all Snap apps use the new prompting system—only those that declare permissions in their snapcraft.yaml. Check the app’s documentation if you’re unsure.
Conclusion
Ubuntu’s refined app permission prompting brings a welcome dose of modern security to the Linux desktop. By empowering you to grant—and revoke—access at runtime, it closes the gap between desktop and mobile operating systems. Follow these eight steps, and you’ll be in full control of what your apps can do, keeping your data safe without sacrificing convenience.
Related Articles
- Bridging the Gap: Why Good Designers Create Inaccessible Websites and How to Fix It
- Mastering Perplexity's Personal Computer Platform on Mac: A Step-by-Step Guide
- Unleash the Force: Top Lego Star Wars Sets for May the 4th
- Safari Technology Preview 243: Top 10 Improvements You Need to Know About
- How to Prevent Signal Message Content from Being Stored in iPhone Notification Database
- Kubernetes v1.36 DRA: What's New in Dynamic Resource Allocation?
- Getting Started with OpenZL 0.2: A Step-by-Step Guide to Meta's Content-Aware Compression
- Windows 11 KB5083631: A Deep Dive into the Latest Optional Update