Tenant IoT Intent Profiles
Create the required tenant default and reusable named overlays for configuration intent.
Enable IoT intent explicitly #
A tenant does not receive an IoT intent profile during onboarding. If the tenant will use IoT configuration or configuration-aware monitoring, an authorized user must explicitly create the first profile and provide its required values. That first profile becomes the active tenant default. Tenants that do not use Cisco Spaces IoT can continue without any intent records.
- Select a supported building or building-equivalent network.
- Open Spaces IoT Configuration.
- Under Building Intent, select Manage Tenant Intent.
- In Tenant IoT Intent Profiles, create and save the tenant default.
Managing these profiles requires controller.manage_spaces_iot_intent_profiles, which is separate from the IoT deployment-management permission.
Tenant-default fields #
| Field | Requirement | Purpose |
|---|---|---|
| Name | Required | Identifies the reusable profile. |
| Beacon Profile | Required | Selects iBeacon or vBeacon behavior. |
| Expected UUID | Required | Beacon namespace expected on managed APs. |
| BLE Mode | Required | Disabled, Scan, Transmit, or Dual. |
| Gateway Mode | Required | Base Gateway or Advanced Gateway. |
| Default Power | Required | Generation default for beacon transmit power. |
| Default Advertising Power | Required | Generation default for advertising power. |
| Default Interval | Required | Generation default for advertising interval. |
| Target IOx Version | Required for Advanced Gateway | Expected Cisco BLE IOx application version. |
| Major | Optional | Default major used when generating per-device intent. |
| Allowed-value lists | Optional | Accepted power, advertising-power, and interval values for monitoring-only fallback comparison. |
| Description and notes | Optional | Operational context for administrators. |
Named profiles and inheritance #
After the default exists, create named profiles as sparse overlays. A blank value inherits from the tenant default. Profiles are location-agnostic until assigned and can be reused by multiple buildings or networks. An edit is live for monitoring-only fallback intent, but it does not alter a published per-device revision.
The tenant default must remain active and cannot be demoted or deleted. Named profiles may be activated or deactivated independently.
BLE and gateway terminology #
| UI value | API value | Meaning |
|---|---|---|
| Disabled | disabled | BLE is disabled. |
| Scan | fullscan | Scan mode; transmit-profile differences are not evaluated. |
| Transmit | transmit | Transmit-only beacon fields apply. |
| Dual | hybrid | Scan and transmit behavior; transmit-only beacon fields apply. |
| Base Gateway | base | Native AP BLE handling; the Cisco BLE IOx application is not expected. |
| Advanced Gateway | advanced | The cisco_dnas_ble_iox_app manages BLE; the tenant default requires a target version. |
Assign a building #
Assign intent from either Building Intent in IoT Configuration or the intent selector in Monitoring Location Configuration. Both edit the same shared building assignment. A blank selector means inherit the tenant default; selecting a named profile creates or updates the override. Intent cannot be assigned directly to a floor.
Monitoring-only fallback intent #
When an observed AP has no published row, monitoring compares it with the effective live profile. This non-exact fallback checks BLE mode, gateway mode, beacon profile type, UUID, and IOx version. In Transmit or Dual mode, observed major and minor values must also be present. Power, advertising power, and interval are checked only when their optional allowed-value lists are defined.
This fallback is always alert-only. It cannot be used for automated remediation.