There's a set of access-related issues I'm opening up. It's not obvious yet what their seperate scopes are, which ones need to be doe together, and in what sequence.
This issue is a parent for them, and to discuss overall strategy.
✨
Make it possible to customise who can administer registrations
Active
Adds an 'administer' operation for registration entities.
May allow the 'administer own $type registration' permission to grant validator & override admin access on registrations the parent has host edit access for.
🐛
RegistrationAccessControlHandler checks 'administer own $type registration' incorrectly
Active
Addresses a bug where 'own' is interpreted as the registrant rather than being based on host edit acess.
Active
3.1
Registration Core
Thanks for creating this issue, I use it frequently to see where things are at.
I started work on some docs on what this should eventually look like when the remaining issues are addressed:
https://www.drupal.org/docs/extending-drupal/contributed-modules/contrib... →