Disable nested create/upsert globally for a model while preserving connect

Nobody has claimed this yet.

Context:
We need to globally disable nested create for entities from any related entities (while keeping only connect), so users can’t bypass business rules by creating entities nested. Example: There is an Items entity with many Blocks. Items can only be created by an admin, while Blocks can be created by any user. We need to ensure a regular user cannot create Items nested when creating Blocks.

Tried:
Using @TypeGraphQL.omit(input: ["create", "update"]) on a relation field (e.g., blocks.item) — this removes the entire relation from inputs, including connect, which doesn’t work for us.
Programmatic applyInputTypesEnhanceMap to hide create/connectOrCreate/upsert/createMany in all nested input containers for Items, keeping connect. This works, but it iterates over all input types in the schema — it’s heavy, and whenever the schema grows, we need to run this again and restrict new inputs.

Question:
Is there a built-in way in typegraphql-prisma, at generation time, to disable nested create/connectOrCreate/upsert for a specific model/relation (e.g., for Items) while preserving connect? Essentially, a “globally disable nested create for model X” switch.
I’d appreciate any recommendations or links to up-to-date examples/documentation for this use case.

Start with the mentioned applyInputTypesEnhanceMap approach and the generator's input-type generation configuration. Determine whether a model- or relation-level generation option can suppress nested create, connectOrCreate, upsert, and createMany while retaining connect; done means the behavior is available at generation time without scanning every schema input type.

Written by the indexing model from the issue text.