Getting started with Studio

Studio is a platform where you can manage your sensors and Cloud Connectors devices, visualize the sensor data, and set up integrations. This article explains the key concepts and shows you how to get quickly started.

First steps

  1. Sign in to Studio
  2. Find your devices 
  3. Explore the Studio features
  4. Understand the Studio key concepts

Step 1: Sign in to Studio

Go to, and sign in using your e-mail address and password.

If this is you or your company's first purchase, the person placing the order receives an invitation to create a Studio admin account for your company when the order is shipped. The Studio admin can invite other team members to Studio after logging in.

No invitation in your inbox?

First, check if any of these common reasons could be the cause for the missing invitation. If none of those apply to you, ask your Studio admin to send a new invitation.

Step 2: Find your devices

When you sign in to Studio, a dropdown where all your projects are listed appears.

Select the project where your devices reside, and you will go straight to the sensor and Cloud Connector overview. 

Where are my newly purchased sensors?

Recently purchased DT sensors are visible in your organization's Inventory project. The inventory project has an mceclip1.pngtag next to its name.

If you have purchased DT sensors through one of our partners, your default project may not have the Inventory tag. If you cannot find your news sensor in Studio, please get in touch with your supplier. 




There are various ways to identify a specific sensor or Cloud Connector, including the inbuilt Identify Sensor by touch function and the QR-code scanner. 

If your devices are offline, install a Cloud Connector to forward the sensor measurements to the cloud.

Step 3: Explore the Studio featuresStudio-Dashboard-Display_672x544.jpeg

Organize your devices

By default, all devices start in the Inventory Project. A great way to keep track of your devices and manage access control on different levels is to create projects to group devices. For the full description, go to this article.

To keep track of your devices, you can add names, descriptions, or labels. See Managing devices in Studio for more information.  

Invite team members

Invite your team members to join your projects. Go to Managing Studio access to learn about the different user roles, add and remove users and resend Studio invitations.

Visualize the sensor data in dashboards

Dashboards are made up of interactive cards and allow for simple analytics. Visualize your project data by building up custom dashboards adding one or more cards. For more information, see How to set up a project dashboard.

Get notified about device states or events

Configure Notifications If you want to get notified about specific device states or events, you can set up custom e-mail notifications. 

For more information, see How to set up notifications.

Export sensor data

Export sensor data for the last 30 days to make reports or study your data in a spreadsheet.

For more information, see How to export sensor data from Studio.

Explore Studio without physical sensors

If you do not have access to physical sensors or would like to test a use case that is not easy to imitate in the real world, create emulated devices and send emulated events. 

Set your Temperature unit preference

Set up your preferred temperature unit in your account profile

Integrate with your platform

If you are using a Cloud Service, you can set up Data Connectors in Studio, which will forward sensor data to the service. Use the REST API or Python API to interact with our services programmatically. 

Step 4: Understand key concepts


The Studio hierarchy has two levels: organizations and projects. An organization is the top-level and can have one or many projects.

The organization represents the legal entity that owns the sensors and receives invoices for device subscriptions. This entity represents an organization, a department within an organization, or an individual.

  • When a new customer buys its first sensors, a new organization is created. Later purchases from the same customer end up in the same organization. 
  • Devices bought are claimed to the organization at shipping time.
  • Users with Administrator Roles for an Organization can access all projects of that organization.



Within an organization, you can have one or more projects where your devices reside. Use projects to group sensors and Cloud Connectors and to manage access control. 

  • The predefined Inventory project receives newly purchased material.
  • A project can only belong to one organization.

User Account

A user account is an identity used to authenticate users who have access to Studio. The user account represents a person.

  • User accounts are global. 
  • Users may have access to projects from different organizations.
  • Roles within a project defines which operation a user is allowed



A device represents a sensor or a Cloud Connector.

  • A device can only belong to one project.
  • Newly purchased devices are in the predefined Inventory project.


Labels are key-value pairs that are useful for adding descriptive data to devices.

  • Each device can have multiple labels.
  • Labels are indexed and searchable in Studio/API.

Service Account

Service Accounts are used to give other services access to projects through the use of APIs. See our guide on Introduction to Service Accounts.

Data Connector

Data Connectors reliably forward your sensor events to other platforms. See our guide on Introduction to Data Connectors.