Prevent Detaching Variables Used in Published Components

Summary

Add an option to prevent variables used in published components from being detached in consuming files.
 

Problem

When a component library is published and used in another Figma file, consumers can detach variable bindings, potentially breaking the intended design system consistency. For libraries that rely on variables to maintain component integrity, this can lead to unintended overrides and make it harder to ensure consistent usage across files.

Proposed Solution

Introduce a setting in the variable's Details panel, such as “Prevent detaching in consuming files.”

When enabled, this setting would prevent consumers from detaching that variable when it is used within instances of published components in other files, while still allowing the variable to be used normally elsewhere.

Ideally, this restriction would apply only to the variable's usage within the relevant published component, rather than globally across every component or property that references the same variable.

Why This Matters

This would give design system maintainers greater control over how their published components are consumed, helping preserve component integrity and prevent accidental detachment of critical variable bindings.

It would be particularly useful for teams building shared component libraries where variables are an essential part of the design system's architecture.