By design, snaps run in isolation from one another and the host system. However, this behaviour can be modified by the snap’s developer in the following ways to meet the requirements of each individual snap:
- devmode can be enabled during a snap’s development to help debug and troubleshoot applications prior to their confinement. Snaps running in devmode have full system access but cannot be published on the Snap Store to a snap’s stable channel.
- interfaces allow a snap to access specific system resource, such as the network or an audio device. Individual interfaces are either enabled automatically or after the user requests a specific connection
classic confinement is a special case reserved for snaps that are unsuitable for strict confinement. Its access to the system is synonymous with the full system access of traditionally packaged applications and requires users to append
For the majority of interfaces, as well as for devmode, there are no special considerations. They can be used to develop strictly confined snaps, access system resources, and publish snaps to the Snap Store without any manual oversight.
However, there are specific circumstances when a manual review and approval process is required, and these circumstances are when a snap requires one of the following:
- classic confinement and publishing to the Snap Store
- automatic alias creation for an executable with a different name to the snap name
(see Application aliases for more details)
- automatic interfaces connection with an interface that defaults to no auto-connection
- a new track, often used to provide a stable version path with production grade applications
- use of a more permissive interfaces, such as personal-files
In general, the approval process requires a forum post making a request by describing the requirement and the reasoning behind it. It then needs approved by the review team.
For next steps, and for more information on what’s required for each type of request, see one of the following forum posts: