You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 22, 2025. It is now read-only.
In addition to allowing frontend authorization on individual content items, it would also be useful if the same settings could be used to configure who should have access to the page's edit form in the admin.
Of course, the ideal extension of that would also be having the ability to filter out such items from lists displayed in the admin, but I'm not sure whether there's even any sort of filtering mechanism like that built into OrchardCore.
The use case is having multiple levels of access in the admin where certain pages are accessible only to the administrator and a specific subset of admin users, but other pages of the same content type will be accessible to everyone who has admin access.
In addition to allowing frontend authorization on individual content items, it would also be useful if the same settings could be used to configure who should have access to the page's edit form in the admin.
Of course, the ideal extension of that would also be having the ability to filter out such items from lists displayed in the admin, but I'm not sure whether there's even any sort of filtering mechanism like that built into OrchardCore.
The use case is having multiple levels of access in the admin where certain pages are accessible only to the administrator and a specific subset of admin users, but other pages of the same content type will be accessible to everyone who has admin access.