Permissions Registry

This W3C Registry provides a centralized place to find the policy-controlled features and/or powerful features of the web platform. Through the change process it also helps assure permissions in the platform are consistently specified across various specifications.

By splitting the registry into standardized permissions and provisional permissions, the registry also provides a way to track the status of these features.

The change process for adding and/or updating this registry is as follows:

1. If necessary, add a "Permissions Policy" section to your specification which includes the following:
   1. The string that identifies the policy controlled feature (e.g., "super-awesome"). Make sure the string is linkable by wrapping it a dfn element.
   2. The default allowlist value (e.g. 'self').
2. Determine if your feature meets the definition of a powerful feature (i.e., requires express permission to be used). If it does:
   1. Specify a powerful feature in your specification in conformance with the Permissions specification.
3. Modify either the table of standardized permissions or the table of provisional permissions filling out each column with the required information.
4. Submit a pull request to the Powerful Features Registry Repository on GitHub with your changes. The maintainers of the repository will review your pull request and check that everything integrates properly.

For a permission to appear in the table of standardized permissions, and thus be considered a standardized permission, it needs to meet the following criteria:

• Implemented and demonstrably interoperable in at least two browser engines (e.g., has accompanying Web Platform Tests).
• Is specified in published as technical report by a W3C Working Group with maturity of first public working draft or above, or is published by the WHATWG as a standard.

Each permission is identified by a unique literal string. In the case of Permissions Policy, the string identifies a policy-controlled features. Similarly, in the Permissions specification the string identifies a powerful feature.

Provisional permissions are permissions that are not yet standardized (i.e., they are either experimental, still in the incubation phase, or are only implemented in a single browser engine).