Skip to content

Latest commit

 

History

History
35 lines (22 loc) · 2.01 KB

permissions.md

File metadata and controls

35 lines (22 loc) · 2.01 KB

Permissions

Permissions allow users to finely control what applications can access, and administrators to finely control what other users can do.

How permissions work

By default, an application has for only right to run code. It cannot interact with any external resource in any way (which means: no window creation, no filesystem/network access, ...).

When an app wants to get a permission, it asks the system to give it.

Levels of permissions

Permissions are split across different level, some being granted automatically based on the circumstances or resulting in a popup being shown to the end user to decide if the permission should be granted or not.

You can find the levels of permissions in the specifications document.

From the control center

Permissions can be revoked at anytime from the control center, allowing to revoke a specific permission for a given application, to revoke a specific permission to all applications (useful for microphone or webcam access, for example) or to revoke all permissions of a specific application.

Security level

The permissions policy depends on the current user's security level, which can be set through the control center:

  • Unsecure: grant all permissions automatically, except privacy permissions
  • Standard (default): grant safe and implicit permissions automatically, but ask for most sensitive and all privacy permissions
  • Tight: only grant implicit permissions but ask for all sensitive and privacy permissions
  • Extreme: only grant safe permissions, ask for every other type of permissions
  • Complete (only available in developer mode): ask for every permissions, including safe ones