VYROX Smart Building
IoTServa Menus, Roles and Control Safety
This guide lists the IoTServa console menus, who can do what and how control stays safe.
Console Menus
| Group | Menus |
|---|---|
| Operate | Dashboards, Overview, Readings (Live Readings and Trends) |
| Manage | Organizations, Site Tree, Floor Plans, Gateways, Sensors, Actuators, Scrapers, Telemetry Points, Node Presets, Device Documents, Rule Engine, Notification Channels |
| Data | Exports, Reports |
| People | Users, User Roles |
| Developer | API Keys, Webhooks |
| Settings | Organization, Billing, Activity, AI, MQTT Brokers, Data Forwarding, Audit Log |
Work Orders and the Digital Twin are also available.
Roles
| Role | What They Can Do |
|---|---|
| Owner | Everything. At least one Owner always remains. |
| Admin | Manage the site, people and settings. |
| Operator | Work with readings and, if allowed, send commands. |
| Viewer | Look only. |
- You can give a person a role for one site only.
- You can create custom roles with finer rights, such as Send Commands, export and billing.
Control Safety Rules
- Control is off for every organisation until an Owner or Admin switches it on.
- Each control point must be enabled and given a minimum and a maximum. Values outside are refused.
- Sending needs the separate Send Commands right.
- Commands are rate limited and expire after a short time.
- After sending, IoTServa reads the value back to confirm it worked.
- Every command is recorded in the audit log, and failures notify the sender.
Rules You Can Build
- Raise Alert, Send Email, Show Popup, Notify via Channel.
- Write Control Point, Call Webhook, Set Variable.
- Create Work Order, Run Another Rule, Escalation.
Frequently Asked Questions
Can the AI Switch Things?
Only if the person asking holds the Send Commands right and every control check passes.
What If Our Plan Ends?
The company becomes read-only and cannot send commands.
Can We Keep Data on Our Own Server?
Yes. Ask about the Private Edition.