New events and actions to get/set webform access group membership

Sorry @joelseguin for my late response, I've missed this issue somehow.

The reason for the model not working as expected is that webform access groups are not content entities, but config entities. Therefore, you should be more successful with the Save config event.

No problem, will test that out and report back.

The "save config" event definitely works nicely with any webform access configuration that has changed - thanks!

However, it seems that the actual users that are added to a Webform Access Group are not saved as config and are not accessible for that reason. Here is an example of a Webform Access Group config. Note that user ids are not stored within config (which completely makes sense):

uuid: ba4ca60a-c97a-48c9-875e-8f05cee3efa7
langcode: en
status: true
dependencies: { }
id: south_region
label: 'South Region'
description: ''
type: regions
permissions:
- create
- configuration
emails: { }

Any thoughts as to how we could access the IDs of users that have been updated? Ultimately, the idea would be to be able to programmatically (via ECA) add/update user IDs based on logic.

We need to find out, how that module stores that data. When we know that, we can build the process.

Hello. The Webform Access Group seems to be "config" and it stores its data in a YML file. However, the Webform Access Group membership seems to be "content" and stores its data in the database table webform_access_group_user.

With ECA we can access config entities and content entities. That means, for the webform access group, ECA can do something with the data. But for Webform Access Group Membership ECA can't as the table structure doesn't appear to be a content entity, it looks more like an arbitrary database table. For that, a specific action plugin would be required to work with that.