Getting started with Studio

Studio is a platform where you can manage your sensors and Cloud Connectors, visualize the sensor data, and set up integrations. This article provides a step-by-step guide for setting up Studio and your devices, allowing you to quickly begin gathering valuable insights.

  1. Log in to Studio
  2. Structure your Organization
  3. Utilize datapoints
  4. Preserve device battery

1. Log in to Studio

Use your Studio Administrator's credentials to log into your account. In case you do not have an account already, sign up for Studio.

If your company already uses DT sensors, request that an administrator include you in the existing Organization by sending you an invite

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 or contact DT Support for help.

Want to use your Identity Provider?

Studio supports the OpenID Connect standard. If you have an Identity Provider that supports it and want to use it to log into Studio, please check the instructions on how to set up Single Sign-On.

2. Structure your Organization

Once logged in, you will have access to all your claimed sensors and Cloud Connectors. If you haven't claimed your devices yet, make sure to do so before continuing. Find instructions for claiming here: Getting started with your first sensors.

  1. Organize sensors and Cloud Connectors
  2. Organize account members
  3. Update billing information
  4. Set up integrations

Organize sensors and Cloud Connectors

Group devices by Projects

The Studio hierarchy has two levels: Organizations and Projects. An Organization is the top-level and can have one or many projects. See the key differences here: Distinguishing Between Organizations and Projects.

All Organizations have a default Inventory project to store all devices that have not been used for installations and do not belong to other Projects.

To start, separate the devices into different Projects. We suggest grouping devices that naturally belong together. For example, you can create Projects to group your devices based on:

  • Location
  • Clients
  • Broken or unused sensors

Advantages of grouping devices by Projects:

Exports and Dashboards - These are restricted to the Project level, providing a more targeted and manageable scope than the Organization level.

Simpler Subscription Management - Active subscriptions can be easily filtered using Project names.

Easier Access Management - Control access by assigning specific members to specific Projects only.

Visit How to create a new Studio project to get started with Projects.

Name your devices

As the next step, we recommend giving the sensors or Cloud Connectors suitable names, descriptions, and labels. That will help with quick identification of your devices after an installation and with device organization. For instance, name your device after its installation location, the client where it is installed, or a combination of both.

Advantages of adding labels to your devices:

Easy Search - Quickly locate sensors and Cloud Connectors with matching label values.

Notifications - Use Labels to automatically include/exclude sensors in notification rules.

Exports and Integration - Label information is included in exported sensor data and integrated with other systems.

Visit Managing devices in Studio to find detailed information on how to name, label, group, and move devices in Studio.

Organize account members

Once your devices are organized, start inviting your members who will manage the devices across the Organization and Projects and decide what access level they will have. 

A user account in Studio verifies a person's identity for accessing the platform and allows them to work on Projects across different Organizations.

Roles assigned within each Project specify what actions users can take. If the Organization has many users, it's advisable to restrict access to the Organization in Studio and provide access solely to Projects.

Consider assigning the Organization Viewer role to stakeholders or upper management who need view-only access to all Projects and sensor data within the Organization. This role excludes access to the Billing module.


Visit Managing Studio access to learn about the different user roles, and how to add and remove users and resend Studio invitations.

Update billing information

The next step is to complete the missing billing information for your account, including:

  • Subscription contact
  • Email for invoice delivery
  • Billing address

Make sure the information is accurate to avoid missing invoices and potential subscription termination due to non-payment.

Set up integrations

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.

3. Utilize datapoints

With your devices now configured, you can begin utilizing the data points to extract value from them:

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 and adding one or more cards. For more information, see How to set up a project dashboard.

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.

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.

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. 

4. Preserve device battery

Store all unused sensors in a cool, dry place at room temperature. To maximize battery life, keep sensors near online Cloud Connectors, as they consume more energy when offline or in Boost mode. This applies to both claimed and unclaimed sensors.

Next steps