Skip to content
This repository was archived by the owner on Dec 22, 2025. It is now read-only.
This repository was archived by the owner on Dec 22, 2025. It is now read-only.

Optionally allow a page to also block backend access in the admin #14

@willnationsdev

Description

@willnationsdev

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions