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

# Glossary

The terms of this application in the meaning they carry here. Where a term means something different in another application, it says so.

| Term | Meaning |
| --- | --- |
| Audit event | A log entry recording who changed what and when. Not editable, exportable, and kept for a limited time. Not every event is visible to everyone — see [Audit events](audit.md). |
| Group | Several users combined, so that roles are granted once for the group instead of per person. Membership is the only thing maintained per user afterwards. |
| Identity | Whoever a role can be granted to — a user or a group. The term appears wherever it does not matter which of the two it is. |
| Infrastructure space | The space an application space obtains its locations, devices, tags and position events from — read-only. One infrastructure can serve several use cases that stay separate from one another: each has its own business data, all see the same location tree and the same devices. The reference is set when the application space is created and cannot be changed afterwards. |
| Invitation | The way a new person enters the system: they are invited by e-mail and set up their own account. An account is not created for them by hand. |
| Onboarding | Inviting a person and setting up their account, up to the first sign-in. Elsewhere: in [IoT Spaces](../../iot-spaces/3.0/glossary.md#term-onboarding) onboarding means connecting a device to the cloud. |
| Permission | What a role is allowed to do with a resource. Permissions are not granted per person but per role, and the check walks up from the resource through its space to the tenant: whoever may act on one level may also act on everything below it. |
| Role | A bundle of permissions that is assigned to a user or a group, for example Space Admin or Tracking Viewer. Roles are the only place where permissions are defined. |
| RTLS | Real-Time Locating System. A system that determines and reports the position of tagged objects continuously. |
| Space | A self-contained working area within a tenant. What it holds follows from its [space type](#term-space-type): the locating infrastructure — a location tree with the devices and scenarios installed there — the business data of an application, or both. A tenant may have several spaces, one per site for example. |
| Space type | Determines the role of a space: **Infrastructure** holds locations, devices and scenarios, **Application** holds the business data of one use case and references an [infrastructure space](#term-infra-space), **General** holds both and is the default. Chosen when the space is created and not changeable afterwards. Each application offers only the types it can work with, which is why the selected space may change when you switch application. |
| Tenant | An isolated organizational unit. Users, groups, spaces, devices, assets and tags always belong to exactly one tenant, and no data is visible across tenants. |
| Trusted certificate | A certificate the platform accepts as proof of identity — for devices that authenticate with a client certificate, and for encrypted connections to other systems. |
| User | A single person with an account. Which applications and which spaces they see follows from their roles. |