Customise accessibility of blueprints based on permissions

[finnjsmith]

There are some blueprints in a collection that I'd like to restrict to a certain sub-set of users, for example some index pages only need to be created once, compared to show pages which need to be created constantly. I think it would be good if there was an option for a blueprint to only be accessible for a user with higher level permissions than someone with simple content-editing permissions in a collection, for example.

I think this functionality would work well with this suggestion too: #1204. They're both centred around the fact that they allow collections to be locked-down by the developers in order to reduce mistakes.

[daun]

For what it's worth, I think ProcessWire has landed on a pretty versatile solution for this.

Each blueprint can define:

• whether other pages can be nested below pages of this blueprint
• whether new pages can be created from this blueprint
• whether more than one page can exist of this blueprint
• which other blueprints are accepted as children or parent of this one

It sounds like a lot, but it allows extremely flexible page trees without editor footguns.