Role topic permissions

Note: You must provide an MQTT topic path.

MQTT topics can contain wildcards such as + and # but can also contain more specific variables:

• {userID} will only match the current user’s ID

• {deviceName} will only match the current device’s name

• {systemKey} will only match the current system’s system key

For example, suppose you have a device named my_device and a topic permission set with publish and subscribe permissions on path /devices/{deviceName}/config. When that device connects to the broker, it can publish and subscribe to the /devices/my_device/config topic but not /devices/my_other_device/config or any other topic path.