This glossary defines the main entities of the Xyte Connect+ platform and the Customer Portal, and establishes the canonical name and capitalization used throughout this documentation. When referring to one of these entities as a named concept, use the form shown here. Terms are grouped by area and listed alphabetically within each group.

Clouds, organizations, and customers

• Cloud — the Xyte instance your Organization belongs to, operated by Xyte or by a Partner. The Cloud name appears beneath the Tenant name at the top-left of the portal.
• Connect+ — Xyte's device management offering for end customers: the Customer Portal, Cloud Connectors, and the Connect+ Edge together. Devices that can be managed on it are listed under Supported Devices.
• Customer — a sub-account inside your Organization, each with its own tree of Spaces, Devices, and Assets. Devices cannot be moved between Customers. An initial Customer named after the Organization is created automatically; integrators and service providers add more, one per client they manage. See Create a new customer and space.
• Customer Portal — the portal where you claim, monitor, and manage your Devices, run Commands, open Tickets, and buy Digital Products. Sometimes white-labeled by the Partner whose Cloud you belong to.
• Managed Service Provider (MSP) — a provider that manages several Tenants and uses the multi-tenant MSP view to work across all of them from one screen.
• Organization — your company account on the platform. It owns everything you see in the portal: Customers, Spaces, Devices, Users, settings, and purchases.
• Partner — a hardware manufacturer (OEM) or solution provider that operates a Cloud on Xyte. A Partner may be granted access to your Organization to provide support.
• Tenant — the Organization currently selected in the portal, shown in bold at the top-left. If you have access to more than one, use Switch Tenant. All information displayed relates to the active Tenant. See Tenant.

Spaces and rooms

• Incident Notification Delay — a per-Space setting (Off to 60 minutes) that governs when an Incident notification is sent, not when a Device is marked offline. An Incident that closes within the delay window notifies no one. See Space Settings.
• Maintenance — a state turned on for a Space or Room while planned work is carried out. Its Devices are not actively monitored and Incidents and Notifications are suppressed. See Set Maintenance.
• Priority modifier — a per-Space setting that raises or lowers the priority of every Incident detected in that Space.
• Room — a Space that holds Devices and represents a physical room. Rooms are the unit that health rollups and Room Statuses are reported on.
• Space — a node in a Customer's tree structure, mirroring your physical setup (site, building, floor, room). Devices are claimed into a Space, and access can be granted per Space. See Spaces.
• VIP Room — a Room flagged as VIP so that it is tracked separately in the Global VIP rooms health rollup on the Customers page.

Users, groups, and access

• API Key — a credential created in Settings that authenticates calls to the Xyte Core API. See API Keys.
• Audit Log — the record of actions taken in your Tenant, such as claiming or deleting a Device. See Audit Logs.
• External Support Access — the setting that controls whether the Partner's support team can access your Devices. See External Support Access.
• External user — a User from outside your Organization — typically a Partner or support User — who has been granted explicit access to your Tenant or to specific Spaces.
• Global Administrators — members of the automatically created administrators Group, with full read and write access to every feature, Space, and Device in the Tenant.
• Global Viewers — members of the automatically created Viewers Group, with read-only access across the Tenant.
• Group — a collection of Users that shares roles and permissions. Access is granted to Groups rather than to individual Users. See Users & Groups.
• Space-level access — permissions granted to a Group on one branch of the Space tree, limiting that Group to the Devices beneath it. See Access Management.
• User — a person with an account on the platform. Users are scoped to a single Cloud.

Devices and assets

• Asset — an inventory record for equipment that is not connected or monitored. Assets need no IP address, MAC address, or connection parameters. See Bulk Add Assets.
• Claim — the act of adding a Device to a Space so that it becomes managed by your Organization. See Claim a device.
• Cloud2Cloud device — a Device that runs on a manufacturer's own cloud and is imported into Xyte through a Cloud Connector. Also written Cloud-to-Cloud, abbreviated C2C. See Claiming a Cloud 2 Cloud device.
• Contract — a business agreement tracked against Devices — support, warranty, discount, and similar — active for a limited period, extendable, and able to raise alerts before it expires. See Contracts.
• Device — a piece of hardware connected to the platform that can be claimed, monitored, commanded, and supported. See Devices.
• Device Model — the specification that defines a family of Devices sharing the same Telemetry, Supported Commands, Rules, and Widgets. Each Device belongs to exactly one Device Model. Often shortened to Model.
• Device status — the single value summarizing a Device's health in the Devices table, combining its self-reported state, the health of the connection carrying its data, and any open Incidents. One of OK, Warning, Error, Device offline, Disconnected, or Never seen. See Device statuses.
• Edge device — a Device on your local network that has no cloud of its own and is monitored through a Connect+ Edge. See Claiming a local network device (Edge).
• File — an asset such as a Firmware image, manual, or script that is stored on the platform and made available to Devices or Users. See Files.
• Firmware — the software running on a Device. Firmware can be distributed and upgraded remotely from the platform.
• Merge — combining entries that represent the same real-world Device but were reported by different Connectors or an Edge, into one Device with a primary instance and one or more secondary instances. A merged Device is counted once for licensing. Split reverses it. See Merging and splitting devices.
• Native device — a Device with built-in Xyte support that connects directly to the platform once it is on the network and its cloud connection is enabled. See Claiming a native device.
• Note — free-form text attached to a Device or a Space to record context for your team. See Notes.
• Room status — the rollup of the statuses of all Devices in a Room, so a Room can be judged usable, degraded, or unmonitored at a glance. See Room Statuses.

Connections: connectors and Edge

• Authorization — the step in which you grant a Cloud Connector access to your account on the provider's cloud, usually by signing in through an authentication link. See Authorizing.
• Cloud Connector — a connection between Xyte and a manufacturer's or monitoring provider's cloud that imports its Devices into your Tenant and keeps them in sync. Each Connector is bound to one Customer and Space. See Cloud Connectors.
• Connect+ Edge — the on-premises software package, delivered as a Docker container, that collects data from Devices on a local network over HTTP, SNMP, and other supported protocols, and enables remote monitoring from the cloud. Install one per physically separate location or network segment. Also referred to simply as an Edge. See Overview.
• Device setup parameters — the per-Model connection details, such as credentials, ports, or protocol options, that an Edge needs in order to reach a Device after it is claimed. See Device Setup Parameters.
• Driver — the per-Device-Model logic that an Edge uses to collect Telemetry and run Commands. A full driver provides rich, model-specific data.
• Edge agent — a single running installation of the Connect+ Edge. Devices are claimed through a specific Edge agent, and each agent has its own Edge ID.
• Heartbeat monitoring — baseline online/offline reachability, available on the Edge for any pingable Device, used where no full driver exists for that Model.
• Secure Edge — a pre-configured physical Edge appliance sold by Xyte for customers who prefer not to run and manage a server themselves. See Secure Edge.
• Sync — the periodic refresh in which a Connector re-reads the provider's cloud and adds, updates, or marks Devices as removed.

Monitoring and operations

• Command — a remote operation sent to a Device to make it perform an action. The set a Device accepts is defined on its Device Model as Supported Commands. See Commands.
• Dashboard — the configurable overview screen for a Space or Device, built from Widgets. See Dashboard.
• Incident — an issue raised automatically when a Rule matches Device Telemetry or a Device becomes unreachable. Incidents carry a priority and are tracked to closure. See Incidents.
• Incident Routing — the per-Space configuration that determines where a Space's Incidents are sent.
• Integration — a connection between Xyte and an external system — messaging, ticketing, or ITSM — used to route Incidents and synchronize Tickets. See Integrations.
• Notification — an alert sent when a platform event occurs, delivered by email, to a messaging Integration, or to a Webhook. See Notifications.
• Report — a summary or Incident digest generated on a schedule and emailed to chosen recipients. See Reports.
• Rule — logic applied to a Device's Telemetry. When a Rule's condition matches, the platform raises an Incident and can open a Ticket or trigger a Notification.
• Telemetry — the time-series key/value messages a Device sends to the platform describing its current state. Telemetry drives Widgets, analytics, and Rule evaluation.
• Ticket — a support request opened against a specific Device and routed to the Partner's support team, with two-way messaging. See Tickets.
• Webhook — an HTTP callback that Xyte invokes on an endpoint you own when a configured event occurs. See Webhooks.
• Widget — a component on a Dashboard that displays Telemetry, status, or other Device data, or exposes a Command. See Widget details.
• Workflow — a scheduled Command that runs automatically, once at a set time or on a recurring weekly schedule. The Space must have a time zone set. See How to Set Up Workflows.

Store and purchases

• Digital Product — software-based functionality, such as a premium feature or a warranty extension, offered for purchase against a Device or Device Model.
• Invoice — the financial document generated for a completed payment. See Invoices.
• License — the artifact issued when a Digital Product is purchased and applied to a Device.
• Order — a purchase transaction for Devices or Digital Products. See Active Orders.
• Plan & Billing — your Organization's subscription tier with Xyte and its billing details. Some capabilities, such as the number of Customers, depend on the plan. See Plan & Billing.
• Store — the catalogue in which you browse and buy Devices and Digital Products offered by your Partner. See Store.
• Subscription — a recurring billing arrangement for a Digital Product, billed monthly or yearly. See Subscriptions.

AI

• AI Teammate — the assistant built into the platform that answers questions about your Spaces, Devices, Users, Incidents, and Tickets, sends Commands, and explains how to use Xyte. See AI Teammate.
• MCP — Model Context Protocol, the open standard by which an AI assistant discovers and invokes tools exposed by an external system. Always written in full capitals.
• MCP server — a process that exposes a set of tools to an AI assistant over MCP. The Xyte MCP server gives your own assistant — Claude, Cursor, or any MCP-capable tool — typed access to your Xyte fleet. Lower-case "server", as it names a category of process rather than a hosted Xyte service.