Allow default workflow assignment to pages ("root" configuration in admin/settings)

[chillu]

It's very confusing that workflow has to be applied to every root page individually. For the similar use case of page view/edit permissions, we have root level defaults in admin/settings.

Also, this means any newly created pages on the root level won't have a workflow assigned by default, which I'd consider a bug - workflow is about enforcing restrictions, including for authors who can create pages (but might not be allowed to publish them in a workflow context).

This is related to the misleading "Inherit from parent" label in the page "Settings" tab: #263

[nyeholt]

It's one reason we use multisites instead of subsites :)

There's actually a branch floating around for doing workflow by-type, rather than tree based inheritance, which may be a useful alternative.

[nzphoenix]

Any update on this? It seems that it would make sense to have a root level Workflow defined in Settings, otherwise "Inherit from parent" doesn't really do anything. As @chillu mentioned, this would stop Content Authors being able to create and publish root level pages (if the default Workflow was set up to require approval from a publisher, etc).

[hp7]

This would be a nice feature. Any luck on fixing this in SS 4^
As default for Page Types (site root workflow); ability to allow Content Author to create page save as draft, but requires approval from Content Editor to publish.