# `IConfiguratorNode.enabled`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Property of [`IConfiguratorNode`](IConfiguratorNode.md) · inherited by [`IGroupNode`](IGroupNode.md), [`IModelNode`](IModelNode.md), [`IMaterialNode`](IMaterialNode.md), [`ConfiguratorNode`](ConfiguratorNode.md) · stable · since 2.0.0

```ts
enabled: boolean;
```

Recorded and priced: false takes the node (and its connections) out of the scene. A node
without it (stored documents may lack it; [`validate('configurator')`](validate.md) and [`setSceneModel`](Writer.setSceneModel.md)
accept it, as 1.x did) is not drawn, as `false` is, and no Problem says so: a node you build
sets `enabled: true`.

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `enabled` names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | not recorded: no ledger row names this member or its owner |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |