What problem does this address?
In the multi-entity editing world, a low-permission user may edit a post that contains high-permission entities like Navigation (see the report by @spacedmonkey, and @getdave's PR with a navigation-specific fix: #37454).
Let's find a way of dealing with permissions in the multi-entity world.
One way to approach it would be to address these use-cases:
- Freezing parts of the blocks that represent the entities the user has no permissions to edit (@talldan mentioned templateLock could be a fit)
- Communicating that the user only has access to edit specific parts of the post (or site)
- Excluding the non-editable entities from the Publish panel
- (ideally) Allow editing an "allowed" entity nested inside a "not allowed" entity
There may be other ways to proceed, too. This issue is about the overarching theme, not any particular solution.
Here are a few specific reports of this problem:
Potentially related issues:
cc @youknowriad @mcsf @mkaz @jorgefilipecosta @draganescu @talldan @mtias @noisysocks @ellatrix @ntsekouras
What problem does this address?
In the multi-entity editing world, a low-permission user may edit a post that contains high-permission entities like Navigation (see the report by @spacedmonkey, and @getdave's PR with a navigation-specific fix: #37454).
Let's find a way of dealing with permissions in the multi-entity world.
One way to approach it would be to address these use-cases:
There may be other ways to proceed, too. This issue is about the overarching theme, not any particular solution.
Here are a few specific reports of this problem:
Potentially related issues:
cc @youknowriad @mcsf @mkaz @jorgefilipecosta @draganescu @talldan @mtias @noisysocks @ellatrix @ntsekouras