Use setup changes when a control device needs actuator or sensor setup added, updated, or retired. A setup change is reviewed before it becomes active setup.
- A control device owner or admin starts from the control device page, opens Control device setup changes, chooses the available action, explains the reason, and submits the setup change package.
- A developer can propose only the setup changes their current role or Technical Support access allows. A control device owner/admin, or bounded Realer staff review when required, accepts setup changes before they apply. Support chat history is useful evidence, but it is not authority by itself.
- Realer checks the current control device, selected setup, device type, plan limits, and Technical Support access again before a submitted package can be accepted by an authorized owner/admin or staff reviewer.
- An accepted add creates control-device setup only. Updating changes only the supported setup fields, and Retire setup removes selected setup from active setup without deleting its history.
Setup changes do not grant resource control, command writes, telemetry access, API secrets, billing access, dashboard membership, firmware updates, marketplace support, or permanent deletion (hard delete). Using new setup on a resource requires separate resource admin approval.
If Realer asks for deployment intent first, use the deployment intent guide to choose between standalone reusable and integrated fixed-device.
Before proposing setup, first design the commands, measurements, and feed data the device should expose.