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.
Why does a resource command need classification?
If you use a resource and see “Command classification missing”, ask a resource admin to review the setup. Resource administration alone does not allow someone to classify the device’s commands.
- An authorized device owner or developer first declares deployment intent if Realer requests it. This describes how the device will be used; it does not classify its commands.
- In Control device setup changes, use the available update action for the actuator setup to propose its command risk class. Assess the whole command; do not choose a lower class simply to enable remote control.
- Open the submitted package for review. An authorized device owner/admin can approve it where permitted; integrated fixed-device setup requires the designated Realer staff review. A developer or Technical Support grant alone does not grant approval rights.
- After approval, a resource admin reviews that resource’s command settings. An accepted risk change makes older policy reviews out of date. Unclassified, high-risk and critical-risk commands remain unavailable for remote execution.
Saving setup or control settings does not send a command or reconnect a device. An active subscription does not replace these reviews or grant resource control.
Review resource command settings