Skip to main content

LayoutLibraryItemUsage

How much depends on one Library node — the delete dialog's input (§5.4).

Product-scoped: products is 1 for a customer's own node. is_in_use is the exception and is computed ACROSS products, because the delete guard refuses on that basis — a Paminga node another tenant references must report as in use here, or the dialog offers a delete the server rejects. The cross-tenant COUNTS never leave the server.

type LayoutLibraryItemUsage {
total: Int!
products: Int!
unattributed: Int!
builders: [LayoutBuilderType!]!
by_builder: [LayoutBuilderUsageCount!]!
is_in_use: Boolean!
constraining_builders: [LayoutBuilderType!]!
}

Fields​

LayoutLibraryItemUsage.total ● Int! non-null scalar​

Assets in this product holding a live reference.

LayoutLibraryItemUsage.products ● Int! non-null scalar​

LayoutLibraryItemUsage.unattributed ● Int! non-null scalar​

Usages whose asset type matches no known builder — a data-integrity signal, not a count of work. Counted in total, absent from by_builder.

LayoutLibraryItemUsage.builders ● [LayoutBuilderType!]! non-null enum​

The builders this node is referenced from IN THIS PRODUCT. Pair it with by_builder for counts; use constraining_builders to decide what an edit may contain.

LayoutLibraryItemUsage.by_builder ● [LayoutBuilderUsageCount!]! non-null object​

Per-builder counts behind builders, same set and same order. Product-scoped, like total.

LayoutLibraryItemUsage.is_in_use ● Boolean! non-null scalar​

LayoutLibraryItemUsage.constraining_builders ● [LayoutBuilderType!]! non-null enum​

The builders an edit must stay compatible with — the palette's input.

CROSS-PRODUCT, like is_in_use and for the same reason: a node referenced from an email breaks that email whoever owns it, so a product-scoped answer would let the editor offer an element the server then refuses. The SET travels, never the counts, so nothing about another product's volume comes with it.

For a node a customer can edit this is identical to builders: their own nodes are invisible to other products, so nobody else can reference one. It differs only for the Paminga shelf, which only an internal user may save.

Returned By​

layoutLibraryItemUsage query

Product

PricingFAQPaminga vs. MarketoMigration CenterMarketo to Paminga TranslatorMarketo Alternative
Paminga Logo
LinkedInFacebookXYouTube
ISO 27001 CompliantSOC 2 Compliant

Built with pride in Denver, Colorado, USA

Copyright © Paminga, Inc. 2026
All rights reserved. Various trademarks held by their respective owners.