General settings, theme, API token, logs and maps
Settings holds Space configuration. Most items require the Admin role; Notifications is also available to Support and Customer (personal preferences for the Space). Templates, organizations, users and billing are covered in their own chapters.
Notifications
Personal preferences for this Space: enable/disable alarm notifications, alternate email and Telegram chat ID. See Notification preferences.
General
Three main tabs:
Labels
- Space name
- How to call assets in the UI (e.g. Assets, Machines, Devices, Plants, Products)
- How to call the hierarchy (Organizations/Groups, Factories/Departments, Brands/Stores, Areas/Zones)
Custom labels appear in menus, lists and messages across the Space.
Branding
Logo (and dark-mode logo), primary/secondary colors. Available on paid plans; Free shows an upgrade prompt.
The Space logo is also used in alarm emails (if missing, a default Trackle logo is used). The Space name (Labels tab) appears in the sender of those emails, e.g. SpaceName ALARM; if unset, Notification is used. See Alarm rules.
Domain
Custom subdomain (minimum 6 characters, with availability check). Does not change the MQTT tenant name.
Theme (appearance)
From the account menu choose Light, Dark or Auto (follows the system). This is a per-user preference, not a General settings item.
API Token
Token used to authenticate devices (e.g. MQTT / integrations that need the Space token).
- Show / hide the value
- Generate or Regenerate (invalidates the previous token)
- Revoke (devices using it stop authenticating)
Treat the token as a secret: anyone who has it can present as a Space device.
Integration logs
Aggregated view of device ↔ Space traffic (in addition to per-asset logs).
Typical columns: date, template, event, status, external ID, asset, message, detail.
Common events: telemetry read/write, device connect/disconnect, asset link/unlink, telemetry discovered. Statuses: Success / Error / Info. Log retention follows the plan.
Maps / OSRM
Used by Map widgets when you enable snap path to road.
- OSRM service URL: if empty, the public demo
https://router.project-osrm.org/route/v1is used - Routing profile: Driving, Foot or Bike
For production traffic, prefer your own OSRM instance.