Skip to content
Customer Portals are now available!Get Started
API Documentation was updated!Learn more

Deployments

A Deployment represents a physical site or installation where devices are located. Deployments are the primary way to organize devices geographically and control access to them.

Think of a deployment as a location:

  • A warehouse running autonomous mobile robots
  • A factory floor with production equipment
  • A customer site where you provide maintenance services
  • A hospital wing with medical devices

Every device belongs to exactly one deployment. Users can have different roles and access levels across different deployments.

Navigate to Deployments and create a new one. Configure at least a name, address, and timezone. All further options — default assignees, notifications, machine data, and customer portal — are found under Settings.

User access to a deployment is managed through Deployment Roles. A user must have an explicit role on a deployment to access its devices and data. A Workspace Admin is automatically given an Admin deployment role on existing and future deployments (which can also be removed per deployment).

See Roles & Permissions for details on deployment roles.

A device can be reassigned to a different deployment if it has been physically relocated. Its complete history is preserved. See Managing Devices.

Spare part stock can also be moved from one deployment to another (you select the source and target deployment). See Stock & Incoming.

A deployment can only be deleted when all of the following conditions are met:

  • No started work orders
  • No open cases
  • No devices

Move or close these items first before deleting a deployment. Deleting requires workspace edit rights.