Editor Permission

Using Neos & Flow
#1

I wanted to revoke Editor to Publish on Live Workspace, but he can publish on another workspace base to Live.

Can anyone help with Policy.yaml or other methods?

#2

Hello, maybe it is helpful for you to use a UI based policy management.
Maybe give https://github.com/sandstorm/NeosAcl a try :slight_smile:

If you need additional help just continue with this thread. :slight_smile:

#3

Thank you, but I’m using Neos 4.0

#4

Neos already has a role “RestrictedEditor”. Just assign it to them and that should solve your issue.

#5

Thank you,
I have created 3 workspace,
Live,
Control{Private}
Editing{Internal}
Editor can access Editing and Control, but cannot publish to Live but can View Live
Restricted Editor only can Edit on Editing, but can view Control and Live

Looking for this solution

#6

So what exactly is not working for you?

#7

I want one of my internal workspace to not edit by restrictedEditor.
How do I restrict workspace for some role.

#8

Trying this POLICY.YAML
‘Plan2net.EditNode:Book1’:
matcher: >-
‘isInWorkspace([“Control”])’
&& ‘isDescendantNodeOf(“aa8e3ae4-8fde-4534-a4d7-fa4bf1d88871”)’

'Neos.Neos:RestrictedEditor':
    privileges:
      -
        privilegeTarget: 'Plan2net.EditNode:Book1'
        permission: DENY

But not working

#9

Hello @sebobo

After server deployment I am facing this issue

Exception #1395869320 in line 258 of /var/www/html/schrackforstudents_cmsbackend/Packages/Framework/Neos.Flow/Classes/Security/Policy/PolicyService.php: privilege target “Neos.Neos:OtherWorkspacesAccess”, referenced in role configuration “Neos.Neos:ShrackEditor” is not defined!

How to resolve this?

Thanks

#10

And locally it works?
Are you dependencies correct and your package depends on Neos?

#11

Yes on local machine it is working fine, on server deployment with new Policy.yaml
the issue started

#12

I assume your composer.lock file or something related to the dependencies is incorrect. Try reinstalling the project locally and see if you can reproduce the error.

#13

Yes composer.lock having typo3/flow
do I need to replace them with neos/flow.
Any example composer.lock where I can see them

#14

Can you help me in that
https://drive.google.com/drive/folders/1I9BfasjGjnKOqDO7ESYgdIUUjNQIlg5r?usp=sharing

composer and lock both are here

Please check and feedback, I am new to neos getting things a bit harder.

#15

Sorry don’t have time right now to look into your files.
You can always check the desired version of the https://github.com/neos/neos-base-distribution repository and its composer files.

#16

Thank You @sebobo
I will look into the GIT link and try to resolve the issue.

Thanks a lot for your help