The Administration application enables account administrators to manage their users, applications, rules and stored files, as well as configure a number of options for their account. Here you can:

For more information on users and permissions, please see the "User and permissions management" guide.

The Home Screen

The "Home" screen provides navigation links to the main parts of the administration application. It also shows subscription information for your account. The subscription information describes how much capacity you have used and the optional applications you are subscribed to. The capacity section shows:

  • API requests: It counts whenever some function in Cumulocity is invoked, regardless of whether the function is invoked from a device (for example, sending a measurement) or from an application (for example, viewing the list of devices).
  • Device API requests: Counted only when the API is called from a device (for example, sending a measurement)
  • Storage: The total amount of data stored in your account. This amount can be changed by retention policies and by the amount and size of stored files.
  • Storage quota: If the storage limit per device is set, the user is restricted to a maximum data usage.
  • Devices: The total number of devices connected to your account. This is the sum of the devices listed in the "All devices" menu of the Device Management application and their direct and indirect child devices.
  • Users: The sum of all users configured in this account, active and inactive.

"This month" shows the usage information starting with the current month. "Last month" shows the last full month.


Viewing audit logs

By visiting the "Audit logs" menu you can view all operations that users have carried out. The following fields can be observed:

  • "When?": Shows the server time when the change occurred.
  • "What?": This field shows what changed. ("Smart Rule Deleted")
  • "Who?": Displays the user who did the change.
  • "Text": Small summary of the change. ("Cep module "smartRule" updated") - "Type": Type of change. ("Smart rule", "Alarm", "User")
  • "Time": Shows the device time when the change occurred. It can be different from the server time.

Only the last 100 logs are visible, in order to view more press the "search more" button.

Audit logs

Filtering logs

In order to easily search through logs, you have the ability to filter them. The following filters can be used:

  • Type: There are six types of logs, "Alarm", "Event processing", "Group", "Operation", "Smart rule" and "User".
  • Date from: Simply select date from which you wish to filter the log.
  • Date to: Select date to which you wish to filter the log.
  • User: View logs of a specific user only.

Filter settings

It is not necessary to use all filters.

To apply filters, simply click on the "Apply filters" button.

To discard filters or to see all audit logs, click on the "cross" button.

Managing applications

Besides the available applications, you can also provide own applications in your account by checking the "Own applications" menu. These applications can be "Smartapps" or generic HTML5 applications. "Smartapps" are HTML5 applications that can be extended by adding plugins. When deploying, the plugins are deployed into a specific application. For example, a plugin might add a specific widget to the Cockpit dashboard.

Plugins can only be added to own applications because the application itself is modified when adding the plugin. When adding a plugin to subscribed applications, the application must be cloned first into an own application. Afterward the plugin can be added. This process is supported by the Administration Application wizard.

"Smartapps" insert the plugin into the application. This has changed from the old Smartapps referencing plugins stored in other applications.

When an application has been created it will be available in the application switcher.

The "Open" button of the application appears when you hover over the application's name.

List of own applications

Creating an application

To add an application, you can upload a "ZIP file" application.

  • Click on "Add application".
  • Click on "Upload ZIP file".
  • Either drop the file into the box or simply browse your computer.

Cloning applications

This option will copy the application. Cloning a subscribed application creates a copy of the application as an own application, with a link to the original application.

In order to clone an application:

  • Click on "Add application"
  • Click on "Clone existing application"
  • Select the desired application that you wish to clone. Note that also subscribed applications are shown.
  • Enter the name of the application. The name will be shown as title on the top left of the application. It will also be shown in the application switcher.
  • Enter an application key. The application key is used to identify requests from this application and to make it available for subscription, see the Concepts guide.
  • Enter the application path. This path will be part of the URL to invoke the application. For example, if you use "hello" as application path, the URL of the application will be "/apps/hello".
  • Click on the "Clone" button.

Adding and removing plugins

In order to configure and extend the function provided with a smartapp, you can add plugins (as ZIP files) to your applications. To add additional plugins, go to “Own applications”, move the cursor over your desired applications and click on “Add Plugin”. You can drag the plugin into the box or just select them from your computer.


To remove a plugin, click on the cogwheel next to the desired plugin and click remove. The following tables list the navigator items, menu items and their respective plugins:

Navigator Item Plugin
Welcome Welcome screen
Home Cockpit Home
Smart Rules Smart Rules UI
Groups Groups Hierarchy
Data Explorer Data Point Explorer UI
Data Point Library Data Point Explorer UI
Reporting Reporting
Reports Dashboard (Note: There are two plugins with this name. Select the one with the description: "Reports are stand alone dashboards without a context")
Alarms Alarm Management
Menu Item Plugin
Info Not possible to disable
Subassets Not possible to disable
Permissions Device Permission Management Plugin
Data Explorer Data Point Explorer UI

Please note the "UI" at the end of the plugin names.

Restoring to an older application version

Users can restore old versions of an application. If you “set active” a specific version of the app, then this will be the version used by users.

Note that the “Archive” tab is not available for subscribed applications, as only the owner of the application can perform this action.

Uploading archives

Multiple archive ZIP file versions can be stored in Cumulocity when they were created by uploading ZIP files. Each version is called an archive. You can upload different versions at the same time and switch between these versions. To upload an archive:

  • Select the application by clicking on its name.
  • Click on the "Archives" tab.
  • Click on "Upload archive" and navigate to the archive in your folder.
  • Click on "Upload" to upload the archive to Cumulocity.

Upload archive

Once uploaded, archives can be downloaded, activated or removed if necessary. The active archive (indicated by a cloud icon) is the version of the application that is currently being served to the users of your account. This version cannot be deleted.

Working with bitbucked hosted application (Deprecated)

Assume that you are developing a web application, using Bitbucket as code repository. In this case, exposing the application through Cumulocity can be done as follows:

  • Click on "Add application".
  • Click on "HTTP(S) proxy".
  • Enter the name of the application, as shown in the application switcher.
  • Enter an application key. The application key is used to identify requests from this application and to make it available for subscription.
  • Enter the application path. This path will b e part of the URL to invoke the application. For example, if you use "hello" as application path, the URL of the application will be "/apps/hello".
  • Enter the server URL where your application is hosted. At this URL, there needs to be an index.html file that provides the entry point to your application.
  • Enter a username to access your repository (optional).
  • Enter a password to access your repository (optional).
  • Click "Save".

https proxy app

Note that, username and password are transmitted using HTTP Basic Authentication.

We do not recommend to use bitbucket hosted application anymore, because downtime of bitbucket results into downtime of the application.

Adding a smartapp (Deprecated)

Note that this functionality is depreciated and will be removed in future versions of the product.

To add a smartapp:

  • Click on "Add application".
  • Click on "Create legacy smartapp".
  • Enter the name of the application. The name will be shown as title on the top left of the application. It will also be shown in the application switcher.
  • Enter the application path. This path will be part of the URL to invoke the application. For example, if you use "hello" as application path, the URL of the application will be "/apps/hello".
  • Click the "Create" button.

Please note that these are the old "Smartapps" in which the plugins that you wish to add to your application must be selected from a list.

Legacy smartapps

Working with external applications

"External applications" are links to applications running elsewhere. Enter name of the application and application key, then provide the URL of that application and click "Save" to make the link available in the application switcher.

Editing applications

To edit an application, simply click on its name. Depending on the type of the application (e.g. Hosted, External), different fields can be modified.

Note that "ID", "Application key" and "Path" cannot be changed once configured.

Removing applications

If you remove an application that overwrites a subscribed application, the currently subscribed application becomes available to all users. Additionally the users will then also benefit from future upgrades of the subscribed application. It is not possible to remove subscribed apps. This is only possible for the owner of the subscribed application.

To overwrite a "Subscribed application" the "Own Application" must have the same context-path as the "Subscribed application".

To remove an application, simply hover over the application name and click on the cogwheel, then press the "Remove" button. A confirmation pop-up window will appear. Click "OK" and the application will be deleted.

Managing tenants

If you are a service provider or subscribed to the Enterprise Edition of Cumulocity, you can manage your own subtenants. You can create subtenants, subscribe them to the applications that you have available and potentially deactivate tenants if they are not in use anymore.

There is an important difference between providing tenants and providing users with different permissions within one tenant. Tenants are physically separated data spaces with a separate URL, own users, separate application management and no sharing of data by default. Users in a single tenant by default share the same URL and the same data space. For example, if your users are separate customers of yours and you need to strictly separate them because they may be competitors, we strongly recommend you to do so by using tenants.

If you would like to use this feature, please contact

To be able to use the functionality below, your user needs to have the appropriate permissions. See "Creating and editing global roles" for information on editing permissions. Since editing tenants is a sensitive operation, permissions for editing tenants are more granular:

  • Read: Browse and view tenants.
  • Create: Create new tenants.
  • Update: Edit tenants (incl. subscriptions) and suspend or activate them.
  • Change: Create, edit and delete tenants.

Browsing sub-tenants

To browse the subtenants, click on the subtenants menu. The panel shows the following information:

  • Tenant status: The small icon indicates the status of a tenant. It can show a green checkmark to indicate that the tenant is active or a red cross to indicate that the tenant is suspended and cannot be accessed.
  • ID: An identifier for this tenant. When you create a tenant, the ID is the first part of the URL. For example, if you create a tenant with the ID "acme" on, the tenant's URL will be "". Note that while you can change the URL later on, you cannot change the ID anymore after the tenant was created.
  • Name: A name for this tenant, for example, the company name of your customer.
  • Domain: The URL that users will use to access this tenant.
  • Contact name: An administrative contact for the tenant.
  • Phone: The phone number of the administrative contact.
  • External reference: A free text field that you can use for arbitrary additional information on the tenant. For example, you can store a reference to your CRM system here.
  • Creation time: The time when the tenant was created.
  • Parent tenant: If you are using the management tenant, you will see an additional column "parent tenant". This column shows the tenant that created the listed tenant.


Adding sub-tenants

To add a new tenant, click on "Create tenant" on the top right of the "Subtenants" panel, fill in the fields and click save. Note that:

  • Tenant IDs must be unique within the system.
  • Tenant URLs also must be unique. You can only use one subdomain level. For example, you can only use "" on You cannot use "". This is not permitted by the TLS standard.
  • You must provide a valid administrator email address to enable users to reset their password.
  • Fields with an asterisk (" * ") are mandatory.

When a tenant is created, it is automatically provisioned with a first, administrative user ("Administrator's username"). This user can create first users and set their permissions. The first user cannot be deleted to prevent you from locking yourself out. You can choose to have the password reset link sent as an e-mail. If you have not selected this option you will have to enter a password and confirm the password. (See "Logging in" for more information on password strength.)

From the management tenant, you can enable other tenants to create subtenants. To do so, check "Allow creation of subtenants".


Editing, suspending and deleting sub-tenants

To edit subtenants, click on the desired subtenant. All the fields can be edited except the ID and the administrator's username. When you have finished editing, click on the "Save" button.

Click on the "Applications" tab to subscribe tenants to applications or remove the applications from the tenant. By default, tenants will be subscribed to the standard Cumulocity applications. To subscribe an application to a tenant, hover over one of the "Available applications" on the right side and click the "Subscribe" button.

Subscribe tenant

To remove an application, hover over one of the "Subscribed applications" on the left side and click "unsubscribe".

Usubscribe tenant

You can temporarily suspend tenants. Suspending tenants blocks any access to this tenant, regardless whether the access is from devices, user or other applications. To suspend a tenant, hover over a tenant in the list of tenants and click the "Suspend" button. Confirm the action by clicking "Ok" and entering your password. The tenant will be shown with a red cross icon. As part of suspending the tenant, an informational email is sent to the tenant administrator if an email address is configured for that administrator.

If you are a service provider, you can suppress this email.

Suspend tenant

If a tenant is suspended, the tenant's data remains in the database and can be made available any time later. To do so, click the "Activate" button.

To finally delete a tenant and remove all the data of the tenant, click the "x" button while hovering over the tenant in the list. This action cannot be reverted. For security reasons, it is only available in the management tenant.

Retrieving usage statistics

The usage statistics menu provides you with information about each subtenant. The statistics show:

  • Id: Unique id of the subtenant.
  • External reference: This field is for individual usage, for example, you can add a link to the CRM system here or an internal customer number.
  • API requests: Number of API requests, including requests from devices and applications.
  • Device API requests: Number of API requests from devices
  • Storage (MB): The amount of data stored in your account.
  • Devices: Total number of devices connected to the tenant.
  • Subscribed application: This column shows number of applications that the subtenant is subscribed to.
  • Creation time: The date and time of the creation of the subtenant.

Usage statistics

Using two-factor authentication

The Two-factor authentication(TFA) is an extra layer of security that requires not only a username and password, but SMS verification as well. TFA can only be set up by administrators. When TFA is enabled, it is impossible to configure it from the "User settings", it is configurable from the administration UI.

Note that a phone number is required when adding a user and TFA is enabled. When users without a phone number try to login using TFA, the user will be redirected to a window, to enter his/her mobile phone number. Without a phone number a login is impossible.

To see whether TFA is enabled for a certain user, go to the "Users" menu and check the TFA status column.

TFA satus

Enable two-factor authentication for a user:

  • Go to the "Users" menu.
  • Click on the user name.
  • Click on the checkbox next to "Enable two-factor authentication.
  • Click "Save".

Enable TFA

Managing event processing

Using event processing, you can specify real-time business logic that is automatically run by Cumulocity as soon as new data arrives or existing data is modified. The logic is deployed in so-called "modules". Modules consist of a set of statements that you write in Cumulocity Event Language. Click on "Event processing" to see the current modules or to create new modules.

Event processing

A user-friendly way to specify real-time business logic is provided in the Cockpit application through the so-called "Smart Rules". Smart Rules are "under the hood" also implemented as Cumulocity Event Language statements, and you can see them when you click on "Event Processing". However, you cannot edit Smart Rules from the Event Processing user interface.

Creating new modules

To create a new module, click on "New module".

  • Enter a name for the module. You can only use alphanumeric characters without blanks.
  • If you want to run the statements in the module immediately, leave the status set to "Deployed". Otherwise, set the status to "Not deployed".
  • Start typing your CEL statements into the large text field labeled "Body". To get some inspiration, select an example from the "Examples" drop-down menu and click "Append example". The example CEL statement will be pasted into the "Body" text field at the position of the cursor.
  • Click the "Save" button.

New module

If you selected the "Deployed" status, you will see a small green "Connected" box in the user interface. Whenever your statements produce some output, you will see it below this "Connected" box. Clicking on a line of output unfolds the detailed output of the statement. Clicking "Clear all" removes the output from the screen.

Managing modules

To modify your module, simply click on the module's name. To remove your module, hover over the module's name and click the "X" button. A confirmation window will pop up. Press "OK" and the module will be removed.

Remove modules

Instead of deleting the module, you can also disable it temporarily by setting the "Status" in the edit menu to "Not deployed". Click on the "Save" button afterward.

Reprioritizing alarms

"Alarm mapping" enables you to change the severity and text of alarms to adapt them to your business priorities. For example, a loss of the connection to a device may be critical to you, but it is, by default, a "MAJOR" alarm. To change this, add an alarm mapping to change alarms related to connection losses to "CRITICAL".

Alarm mapping

Adding an alarm mapping

To modify the severity of an alarm, determine the type of the alarm that you want to modify by clicking on an alarm in the alarm list. Then click "Add alarm mapping" in the "Alarm mapping" menu.

  • Enter the alarm type to modify.
  • Select desired new severity, or select "Drop" to not show the alarm at all.
  • Enter a new text for the alarm. This step is optional. If you do not enter any text, the original text in the alarm will be preserved.
  • Click "Save".

Changing or deleting alarm mappings

To change an alarm mapping,

  • Locate the alarm in the "Alarm mapping" section and click on its name.
  • Change the severity and/or text.
  • Click "Save".

To delete alarm severities, hover over the alarm type and click the "X" button. A confirmation window will pop up. Press "OK" to delete the alarm mapping.

Changing settings

By expanding the "Settings" menu, administrators can:

Changing the password policy

To change password settings, click on "Password". To limit the validity of user passwords, set the number of days when users have to change their passwords. If you do not want to force your users to change passwords, use "0" for unlimited validity of passwords.

By default, users can use any password with eight characters or more. If you select "Enforce that all password are "strong" (green)", your users must provide strong passwords as described in "Logging in".

"Enforce that all password are green" and the "Password validity limit" can be mandatory and non-editable, if configured by the platform administrator.

Strong (green) passwords must have M characters. By default, the system restricts users to not use passwords used in history, in other words, last N passwords provided by a user are remembered by the system and the system restricts users to not use them. The default value for N is 10.

"M" and "N" can be configured by the platform administrator.

Click "Save" to store the settings.

Password settings

Changing the TFA settings

To change the TFA settings, click on "Password" under the "Settings" menu item. There are two TFA settings that can be changed:

  • "Limit token validity"- You can set the lifetime of each session. When the session expires, the user has to enter a new verification code.
  • "Limit PIN validity"- Set the lifetime of each verification code sent via SMS. When the verification code expires, in order to login the user has to request a new verification code.
  • When ready, click "Save TFA settings".

TFA settings

To disable two-factor authentication, simply deselect the box "Allow two-factor authentication". Click on "Save TFA settings" to apply your changes.

Changing the default application

With the "Application" menu, administrators can change the default application view for all users within the tenant when no application was defined in the URL. All users also must have access to this application.

Changing access control settings

With the "Application" menu, administrators can enable cross-origin resource sharing or "CORS" on the Cumulocity API. For more information, see

Enabling server-side agents

In the "Server-side agents" menu, the "Send dashboard via e-mail" smart rule can be enabled or disabled. To enable, select the checkbox and click "Save".

Enter OpenIT credentials

SMS sending is used by several features within the application. It can be used to make login more secure with two-factors authentication. An SMS can be sent when an alarm is triggered. SMSes can be used to send instructions to devices. The service provided by Openit can be used similar. In this section, the user can enter credentials to activate features requiring SMS messages.

Managing data retention

"Retention rules" gives you control how long data is stored in your account. For example, you want to store measurements for 90 days, but delete alarms already after 10 days. By default, all historical data is deleted after 60 days (This can be edited in system settings).

Retention rules are usually run during the night. When you edit a retention rule, you will not see an immediate effect in the usage section on the home page of the administration application.

Add rule

To add additional "Retention rules", click on "Add rule". Up to the "Maximum age" field, you can enter an asterisk ("*") into all fields to permit any value in that field.

  • Select the type of data to clean up (alarms, measurements, events, operations, audit logs).
  • Enter a fragment type, if you want to be more specific about the data to be cleaned up. To clean up all connection loss alarms with this rule, select "alarms" and enter "c8y_UnavailabilityAlarm" into "type".
  • If you want to remove only data from a specific device, enter the device ID into "Source".
  • Enter the "Maximum age" in days (max. allowed value is 10 years in days).
  • Click the "Save" button.

Add retention rule

Note that alarms are only removed if they are in "CLEARED" state.

To delete a rule, click on the "X" button and then press "OK" after the pop-up window appears.

Managing storage quota warning e-mail

This section is only visible if a storage quota was set for the tenant. The tenant administrators can set a user group and threshold for an e-mail to be sent once a day if the storage used is higher than a percentage of the storage quota. The e-mail warning can also be disabled. The default setup is sending an e-mail to the "admin" group when the storage reaches 80% of maximum storage.

Managing files

The file repository provides an overview of the files stored in your account. To see the files, click on "Files repository" in the administration menu. The files listed can come from various sources. They can be software images, configuration snapshots taken from devices, log files from devices or web applications uploaded using the "Own applications" menu. To delete a file, click the "X" button next to the file.

Files repository

If the file corresponds to an active application, it cannot be deleted. You first need to remove or upgrade the application to be able to delete it.

Storage quota

The storage quota is in place for a tenant when a storage quota per device is set by the platform administrator. The total storage available to the user is calculated using the formula storage quota per device x number of devices. A check is performed every night to ensure the quota is not exceeded.

In case the quota is exceeded, an e-mail is sent to all tenant administrators to warn them that data will be deleted the following night. After 24h, if the quota is still exceeded, all data retention limits are reduced by a fixed percentage. The storage quota per device will be reduced as a result of this rule.

Let us assume that a tenant has a storage quota of 10GB. Retention rules are 80 days for measurements, 90 days for all other data.

  • Day 1: In the nightly check, the total storage is calculated at 13GB. An e-mail is sent to all the tenant administrators.

  • Day 2: the total storage is still at 13GB. The system determines that a 15% reduction of the retention rules is sufficient to be under the storage quota. So any measurement older than 68 days (80 days - 15%) and any other data older that 77 days (90 days - 15% results in 76.5 days, rounded to 77 days) is deleted.

The total storage is now at 9.8GB.