Provide the client with permissions flags for create content

Should this be postponed on 📌 Allow XB to be used on all node types Active

I think we should still do this for page + node--article, even if 📌 Allow XB to be used on all node types Active would definitely need to refactor this.

This is a because without this, the following will always be visible:

Secondarily, this hard-blocked 📌 Add generic create entity support Active .

Adjusted the proposal.

Note that this can assume a single XB field per content entity type+bundle, if that changes in 📌 Spike: explore merits of one XB field per exposed slot in content templates Active , it'll be up to that issue to tweak the logic introduced here.

Looks great!

One question, plus needs a follow-up for fixing cacheability.

Already approved 👍

Back to Wim per !1178.
I'm 50% on each option, so your call. The client UI will probably need to check the absence of the key anyway.