---
title: Overview
id: "en:tpm:ROOT:index.adoc"
site: en
component: tpm
module: ROOT
version: 3.0
lang: en
url: "https://help.rtlscloud.io/en/tpm/3.0/index.html"
source_repo: "https://github.com/iot-invent/rtlscloud-tpm.git@3.0.x"
source_path: docs/en/modules/ROOT/pages/index.adoc
---

# Overview

Tag Provisioning and Management looks after tags that talk to the cloud directly over a cellular connection — with no equipment to install at the site. It derives a position from what a tag observes and makes it traceable how that position came about.

-   Tags appear on their own as soon as a device reports for the first time

-   Groups control which third-party system receives which events

-   A position database of your own for beacons, WiFi access points and mobile network cells

-   Decision events show, for every single position, where it came from

-   A position cache recognizes known environments and saves chargeable requests

-   Full separation by tenant

## Structure of the Application

| Area | Description |
| --- | --- |
| [First Steps](firststeps/firststeps.md) | The path from a device’s first report to the third-party system receiving its positions. |
| [Tags](tags.md) | The working list of all tags of the current tenant, with state, telemetry and assignments. |
| [Tag Groups](tag_groups.md) | Creating and maintaining groups. They are the unit by which access is authorized. |
| [Decision events](decision_events.md) | The diagnostic view: every positioning decision with the data it is based on. |
| [Clients](clients.md) | The credentials third-party systems use to collect positions and decisions. |
| [Custom Locations](custom_locations.md) | Your own position database — cells, WiFis and beacons with a known position. |
| [How a Position is Determined](positioning.md) | The order in which the application consults its sources, and what that means in practice. |
| Administration | Views across all tenants and the maintenance of the position cache. Requires the cloud administrator role and is opened through the gear icon in the side menu. |

> **NOTE:** If you are new to the application, start with First Steps. The order of the steps there is not arbitrary — without it the tag list stays empty, or no events reach the target system.

## What This Application Does Not Do

-   It shows **no floor plans or indoor maps**. Positions are geographic coordinates on a world map. For locating within buildings there is the tracking application.

-   It has **no location hierarchy** of plant, building and floor. Separation is by tenant only.

-   It offers **no interface for querying the past**. Third-party systems receive events continuously; whoever needs history stores it themselves.