---
title: Decision events (Administration)
id: "en:tpm:admin:decision_events.adoc"
site: en
component: tpm
module: admin
version: 3.0
lang: en
url: "https://help.rtlscloud.io/en/tpm/3.0/admin/decision_events.html"
source_repo: "https://github.com/iot-invent/rtlscloud-tpm.git@3.0.x"
source_path: docs/en/modules/admin/pages/decision_events.adoc
---

# Decision events (Administration)

Decision events across **all tenants**. Handling and detail dialogs are identical to [Decision events](../decision_events.md) in the work area; only the data basis is broader and a tenant filter is added.

## What This View is For

Two cases the work area cannot cover:

-   A device is **not yet assigned to a tenant** and is therefore invisible in any work area. Whether it delivers sensible positions at all can only be checked here — and that is the precondition for handing it over with confidence.

-   A problem affects **several tenants**, for example a wrong entry in the shared position cache. Only the cross-tenant view shows it is not an isolated case.

## Reference

![Decision events (Administration)](_images/tpm_app_admin_decision_events.png)

Columns, detail dialog, context menu and retention are described under [Decision events](../decision_events.md).

## Additional Filter

| Filter | Description |
| --- | --- |
| Tenant | Restriction to one tenant. Without a selection, all are shown |

## Create Request

The **Create request** action — a one-off, chargeable lookup at an online service with the data of a specific event — is available only in the administration area.

It does not change any stored position, only shows what the service would say about this raw data. This is the way to check an assumption before deleting a cache entry or creating a position of your own.