With Ubidots, users self-design IoT and Cloud applications. All Ubidots users begin with a 1 App which can contain multiple Organizations, Devices, Dashboards, and Users. This article is meant to help you better understanding and distinguish these terms in order to keep your Ubidots account and its Apps' architectures organized and your users engaged.

Table of Contents

  1. What is an IoT Application
  2. Essential IoT Components
  3. Apps
  4. Organizations
    - Organizations as Customers
    - Organizations according to a Corporations different departments
    - Organizations as end-users
  5. Users (end-users)
  6. What is the difference between an App and an Organization?

What is an IoT Application?

An IoT or Cloud Application is any program that performs X function with the intention of receiving Y results. IoT Applications generally incorporates sensor data to perform any number of functions. Cloud Applications are a combination of physical sensor data combined with digital data (e.g. real-time stock or gas prices) to realize additional insights beyond the raw data from the sensors. Here are a few applications already live today.

Essential App Components

The Ubidots IoT Application Development and Deployment Platform maintains the following components and tools:

  • Dashboards: display sensor data in in widgets for visualization and computation.
  • Alerts (or events): actions triggered when data readings fulfill or exceed a design rule. Alerts include SMS, Telegram, WebHook, or setting up a new variable. (e.g. send an alert when a device stops sending data). 
  • Analytics: mathematical, statistical, and serverless cloud functions to extract, transform, schedule, and analyze data.
  • Exporting: Ubidots let you export your data in CSV files
  • Sharing capabilities: Ubidots let you share via embedding URLs into a websites HTML.
  • User Management: An Administrator grants custom access and interaction capabilities for a given user.
  • Device Management: Ubidots' platform lets you control remotely your devices from the front end. E.g.: switches off/on your devices with a simple switch in a dashboard.


Apps are the foundational structures in Ubidots and can house different Organizations and Users. Different applications allow user to brand or white-label two, or more, Apps to be accessed by multiple different end-users. All Ubidots accounts begin with a single App. 

Most Ubidots accounts operate with a single App, branded to their own company's likeness with multiple Organizations that sub-divide the App into different access levels of devices, dashboards, alerts, and end-users.

When might I need a second App? 

One question we get a lot at Ubidots is when to purchase a second App vs. the free second Organization. Simply, if you wish to apply different, customized white-label branding experiences for end-users, then a Second App is required. For example, if you wish to deploy App 1 to your client ABC Hospital with their own branding and logos to monitor beds and then another client, XYZ Care, also wants a bed monitoring App, they too may have their own branding applied, only requiring the Ubidots Admin to create a second App. Alternatively, if your two clients simply wish to monitor beds and access their Dashboards, Devices, and Data via the same branded application under your Company's branding, this can easily be done with a single App and multiple Organizations.

If you would like to deploy a second App, please reach out to Ubidots and a member from our DevOps team will deploy your second application within 48 hours of the request. Please note a second application is accompanied by a $49/month fee. For any additional billing inquires, please see the Ubidots pricing.


In Ubidots, an organization is any entity that manages users, devices, dashboards.

An Organization refers to an entity, e.g., company, a specific department, or a set of IoT devices and variables specific to a specific user roles within an App. Each Organization can have its own specific users, devices, dashboards, and more. Admins of Ubidots can sub-divide an App into Organizations based the Application's intended user experience and application design. After all - with Ubidots - the user is the App architect, designer, and builder.

One might think that an Organization might refer to a company, but in Ubidots an Organization is any structured entity with users, devices, and dashboards. 

Here are some different ways to conceptualize an Organization:

1.- Organizations as customers

Sell applications or allow customers to develop their own

ABC company provides tank monitoring devices connected to CO2 Air tanks to multiple local hospitals and uses Ubidots to remotely monitor each tank's pressure, location, and usage. In this use case, each hospital is assigned the same App within Ubidots, but each hospital is classified as a separate, individual Organization that would look as such: ABC Company has 1 APP with Hospital X, Hospital Y, and Hospital Z as 3 separate Organizations – each having access to only the devices located in their facilities.

2.- Organizations according to a Corporations different departments

Build an IoT solution for each department in a corporation.

A manufacturing plant wants to implement an Internet of Things applications in different areas across their company. They look to track their outbound shipments for the logistics department, monitor production output based on product counters and machine uptime statuses for the OT departments, and help the HR department improve wellness in the workplace by ensuring workers safety with mandatory break or rest periods. 

In this use case, the Corporation may purchases a Ubidots license and creates 3 organizations: Logistics, Production, and HR. Each having their own access to devices and data relative to their department and the data needed to best serve that Department. 

Here, it is important to note that even though the applications for each department are different, the entirety of the Corporation's data can still be housed into a single App controlled by the Ubidots Administrator. 

3.- Organizations as end-users

Deploy IoT solutions as a product with each end-user registered as an organization with one or more single devices

For OEMs and businesses using Ubidots to deploy end-user friendly products. Each organization be seen as a single end-user and device, and can automatically assigned using different Organizational TOKENS. If this model matches your business plan, please contact Ubidots sales for additional questions and to receive a tailed pricing plan for your IoT solution's deployment.

Users (end-users)

Users are any entry with assigned credentials to an individual as a Username, Email, and Password who can access your Ubidots Apps.

To create and manage users, check out this tutorial for more details.

Users are the individuals interacting with Ubidots powered Apps. Users can be collected into Grouped permissions, or each user can be given customized access or restrictions to any aspect of an App. The difference between Users and Organizations is that Organizations determine what dashboards, devices, alerts, and other elements the Users can interact with.

All Users, at the time of publishing this article, must be self created by the Ubidots Admin. For additional information to setting up an End-User in your Ubidots account, check out this helpful tutorial.

What is the difference between an App and an Organization?

An App is any user access portal that can be accessed by an end-user within an Organization. On the other hand, an Organization is a group of users that only has access to the devices, dashboards, and events provisioned by the Administrator of an Ubidots account. 

Apps being the parent of Ubidots' architecture, it is true that all Apps can have Organizations, and it is also true that no Organization can exist without a parent App.

To continue learning the Basics to your Ubidots account, have a look at the following articles to expedite your development.

Ubidots Basics: Devices, Variables, Dashboards, and Alerts Explained

Ubidots User Management

Events: Creating Conditional Events and Alerts

Did this answer your question?