Permissions, multiple contexts, read only and context managers

[halftrainedharry]

@andreasz

it will only be working if it’s in the mgr profile and not in the context-specific one.

When you work in the MODX manager, the current context is “mgr”, and when you save a resource, it is only checked if you have the save_document permission for the “mgr” context (no matter in what context the resources was created).

Having the save_document permission in another context (like e.g. “web-nl”) would only be relevant, if you accessed the resource on the front-end and then (for example) checked this permission in a snippet ($modx->hasPermission('save_document')).

---

I think the only way to restrict a certain user in the manager from editing resources in a certain context, is to not give them any permission to that context.

See also this older thread:

How to narrow editing resources roles by context

We currently maintain a MODX 2.6.5 installation with multiple contexts, each one related to a different portal (and accessed by a specific user group). We created a Content Editor role to allow some users in each portal to edit page content. However, when one such user logs in the manager context, they can see (and modify…) resources from ALL contexts. I have not been able to find a way to limit their access by context. I suppose this should be a common issue for MODX administrators, but I hav…