- Issue created by @marco.b
- ๐บ๐ธUnited States partdigital
Hi marco.b
Right now the selection sets are not fully baked for dynamic mode. For example, it doesn't constrain which fields you can use if they are not supposed to be part of the same set. If you need to use selection sets I highly recommend using Manual mode.
FWIW in version 2.0 I am currently working on the ability to use manual mode from the node edit page. You'll no longer need to go to the Access tab. This is to address a common issue where some users want to have more control of access on insert instead of update. Would that help with what you're trying to achieve?
- ๐ฉ๐ชGermany marco.b
Hi partdigital, thanks for the reply.
My bottleneck is that for my use case, I need to assign multiple access policies to some nodes, but I want this to happen dynamically by setting field values โโor generally when creating nodes, without the user being able to influence it.
An ECA module integration would be ideal for this, so that there is an ECA action that allows multiple access policies to be added to a node in an ECA model by entering the machine name, separated by commas.
Would such an integration perhaps be of general interest?
- ๐ฉ๐ชGermany marco.b
As far as I know all actions that are available in core are also available as actions in ECA.
So maybe an action plugin that presents actions like "Assign access policy POLICE_NAME" could also be used as an ECA-Action and also as an action for node bulk editing of selected nodes in a view, isn't it?
- ๐ฎ๐ชIreland marksmith
The integration of access_policy with ECA would be really great! There are lots of cases where assigning an access policy to a node would be part of an automatic workflow, like automatic node creation, bulk operations, etc. Another access control module (Content access) already has an ECA submodule โ . From a user's perspective the complex needs that can be covered by the Access Policy module cannot be fulfilled by Content Access. So looking forward to this feature as well.