The goal is described in this UX design page: http://wiki.magnolia-cms.com/display/UX/How+ACLs+are+defined+to+restrict+access+to+nodes

Development is happening on the 'acls' branch.

Web Access Control

• We add this as a separate tab with a dedicated field

ACLs

• Each workspace/ACL will have its own field
• The label of these fields are the workspace names
• The fields are created dynamically rather than configuring them, by either:
  • using a dynamic provider, similar to configuration-by-code, or
  • by creating a definition in the edit action, like in pages app for adding components

Update: we're not using a provider to add fields because it would be overwritten when the configuration in workspace changes. Instead the action reads a fresh dialog definition from the workspace and then adds the fields. This also means we don't have to require fields to be clonable.

Choose dialog

• problem:
  • not all workspaces have an app
  • not all choose dialogs return a path (DAM returns an asset id)
• solution
  • we construct a choose dialog
    • uses a generic workbench configuration
    • the configuration is build by code