Module Description
The Flexible permissions module allows you to gather, calculate and cache permissions from a myriad of sources. By virtue of a centralized permission checker service, it enables you to turn your website's access control layer into a Policy Based Access Control (PBAC).
For instance, you could have no editors be allowed to edit any content by default, but have a permission calculator that adds these permissions during office hours. The cache (built using VariationCache) would be smart enough to recognize this and serve the user a more permissive set of permissions during office hours, allowing them to edit content.
Right now, the module needs to be implemented by any access defining module such as Group, Domain, Commerce Stores, etc. The Group module already relies on this module as of version 2.0.0.
Scope based permissions
You can define permissions for each scope. Scopes are a way to determine where the permissions should be checked to give access. Your regular Drupal permissions could be regarded as being in the "default" scope, but each implementation is free to add their own scopes.
As an example: The Group module does not check for regular Drupal permissions. Instead, it has its own permission layer where access is checked versus group types when you are or aren't a member (group_outsider and group_insider scopes) and against individual memberships (group_individual).
The Domain module would be able to define permissions specifically for certain domains and Commerce would be able to do the same on a per-store basis.
Core integration
This module has been sponsored to be turned into a core system: #3371246: [Meta, Plan] Pitch-Burgh: Policy based access in core It is therefore advisable to carefully consider starting a new project using this module. Things are looking like this might get into core with some class name changes and adjustments to the order of parameters. So you might want to wait for core to offer this functionality. if you are using this module because of the Group module, don't worry. We will try and come up with an upgrade path for you.
Sponsored by Factorial GmbH This project is sponsored by Factorial GmbH. Drop us a line if you are looking for interesting open source employment.
For instance, you could have no editors be allowed to edit any content by default, but have a permission calculator that adds these permissions during office hours. The cache (built using VariationCache) would be smart enough to recognize this and serve the user a more permissive set of permissions during office hours, allowing them to edit content.
Right now, the module needs to be implemented by any access defining module such as Group, Domain, Commerce Stores, etc. The Group module already relies on this module as of version 2.0.0.
Scope based permissions
You can define permissions for each scope. Scopes are a way to determine where the permissions should be checked to give access. Your regular Drupal permissions could be regarded as being in the "default" scope, but each implementation is free to add their own scopes.
As an example: The Group module does not check for regular Drupal permissions. Instead, it has its own permission layer where access is checked versus group types when you are or aren't a member (group_outsider and group_insider scopes) and against individual memberships (group_individual).
The Domain module would be able to define permissions specifically for certain domains and Commerce would be able to do the same on a per-store basis.
Core integration
This module has been sponsored to be turned into a core system: #3371246: [Meta, Plan] Pitch-Burgh: Policy based access in core It is therefore advisable to carefully consider starting a new project using this module. Things are looking like this might get into core with some class name changes and adjustments to the order of parameters. So you might want to wait for core to offer this functionality. if you are using this module because of the Group module, don't worry. We will try and come up with an upgrade path for you.
Sponsored by Factorial GmbH This project is sponsored by Factorial GmbH. Drop us a line if you are looking for interesting open source employment.
Module Link
Project Usage
2566
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
The Flexible permissions module aims to solve the issue of gathering, calculating, and caching permissions from various sources to enable Policy Based Access Control (PBAC) on a website.
Data Name
flexible_permissions
OPENAI CHATBOT
OPENAI CHATBOT
