Platform administration

The Administration → Admin navigation group is visible only to platform administrators. The Platform API enforces the same restriction; hiding the navigation is only a convenience.

Import an IOTA snapshot

The IOTA snapshot import creates a current working set of device types and devices from the old IOTA platform. It is a temporary V1 migration aid, not a continuous synchronization.

1. Select the destination tenant in the sidebar. For the Burgenland migration, select gesundheit-burgenland.
2. Confirm that the destination tenant shown on the Admin page is active.
3. Enter the IOTA base URL, username, and password. The expected base URL is https://commonapi-gesundheit-burgenland.xaas-a0a0.cloud/api.
4. Select Import devices and device types.
5. Verify source and destination in the confirmation dialog, then start the import.
6. Review the created, existing, and skipped counters and the issue table.

The login may see several IOTA tenants. The importer deliberately combines all of them into the selected SENS tenant. Credentials remain in this browser form only for the attempt and the password field is cleared immediately afterward.

What the import changes

• The trimmed IOTA device-type code remains the visible name. Codes that do not already match the SENS key format receive a deterministic readable slug plus a collision-safe hash as their immutable key.
• A valid IOTA device edid becomes the normalized, uppercase DevEUI.
• The trimmed IOTA serial becomes the device name; an empty serial falls back to the DevEUI.
• New records are active, have empty metadata, and devices have no organization assignment.
• IOTA asset types, their asset pseudo-devices, and devices connected directly to those assets are excluded.

The importer never changes or deletes existing SENS data. A device already in another tenant is not moved. Disabled types are not reactivated. Invalid EDIDs, missing type references, contradictory duplicate DevEUIs, and other source problems are skipped and listed after the run. If database or audit persistence fails, none of the valid candidates from that attempt are stored. Identical trimmed type codes from any number of visible IOTA tenants always map to one destination device type.

An IOTA connection error includes a correlation ID when available. Keep that ID for support, verify the source URL and credentials, and try again. Do not paste credentials into support tickets.