Content
Introduction
The core data in Allthings forms the basis for a structured and cross-channel use of the platform functions. Correct structuring is crucial to be able to manage concerns, posts, documents, bookings, or users in a targeted and efficient way.
The core data follows a hierarchical structure with a total of four levels:
-
Level 1: App
The entire application, which includes all properties and units. -
Level 2: Street / Property
A specific property or street within the app. -
Level 3: Building / Address
A specific building or address within a property. -
Level 4: Residential unit / Offices / Companies
Individual apartments, offices, or companies within a building.
Note: A clean and complete core data structure is a prerequisite for the use of tags, automated ticket distribution, and channel-based content visibility in the app. You can find more information about the term "channel" here.
Core data of residential properties
Relevant core data is stored for each apartment. This includes unique identification numbers (Unit IDs), building data, and other content. This data is important, for example, to assign requests in issue management to a unique Unit ID. This core data is also relevant for future adjustments, tenant changes, new tenants, etc.
Below you can see the structure for an app for a single property.
The structure for an app for multiple properties (Portfolio) looks like this:
Core data of commercial properties
Relevant core data is stored for each office/commercial space. This includes unique identification numbers (Unit IDs), address data, and other content. This data is important, for example, to assign requests in issue management to a unique identification number. This core data is also relevant for future adjustments, office changes, new offices, etc.
Below you can see the structure for an app for an office building:
The structure for an app for a commercial park looks like this: