Content
Overview
The Resident management section in Allthings Cockpit allows you to view and manage which units and apps each person is linked to. The detail page of a resident is divided into three areas:
- Periods — all active and archived links between the person and units in one or more apps.
- Ticket overview — all previous requests submitted by the person through the app. This section additionally requires the "Issue management | Manage tickets (Team member)" permission; without it, the section remains empty.
- Person details (right column) — app profile, phone numbers, additional email addresses, ERP ID, language setting, and email notifications.
To access the detail page, go to Resident management → All residents and click on the name of the person you are looking for.
Periods
The Periods section lists all links between the resident and their units. Each row represents a period — the time span during which the person is assigned to a specific unit within an app.
The table contains the following columns:
- App — the Allthings app the unit belongs to
- Address — address of the property
- Unit — the specific residential unit
- Period — start and end date of the link; open means no end date has been defined yet
- Type — type of occupancy, e.g. Rental
- Registration status — shows whether the person is registered in the app (e.g. Registered)
Use the Show archived data checkbox to display expired periods.
Add period
To link a person to a new unit, click Add period. The Choose periods dialog will open.
The dialog displays the app structure as a tree view — from the app down through properties and buildings to individual units. Only units are selectable. Expand the tree and select the desired unit.
Confirm your selection with Add or cancel with Cancel.
Note: This dialog only links the person to the unit — it does not set a start or end date. To set or change the start and end date of a period, use the unit in the master data.
Delete period
To remove an existing period, click the menu icon (···) in the corresponding row and select Delete this period.
Warning: Deleting a period permanently removes the link between the person and the unit. This action cannot be undone. If you delete a resident's last remaining period, Cockpit automatically returns to the previous view.
Ticket overview
Below the periods section, the Ticket overview shows team members with the "Issue management | Manage tickets (Team member)" permission all requests that the resident has submitted through the app. For each request, the message, category, creation date, and date of the last status change are displayed.
The ticket overview helps you quickly get context when contacting residents — without having to search separately in the issue management section.
Person details
The right column shows the Person details section with app-specific and personal data for the resident.
App profile
The App profile section shows the alias of the resident. The alias is a self-chosen display name used in the app when interacting with neighbours — instead of the person's full name. If no alias has been set, the field remains empty.
The alias cannot be edited here. Residents set their alias themselves in the app profile settings.
Manage phone numbers
The Phone number section allows you to store one or more phone numbers for the person.
- The Default Phone Number is used for notifications and contact purposes.
- Use Add new phone number to add an additional number. When doing so, you also select a Type (Landline Private, Mobile Private, Landline Work, or Mobile Work).
- Existing numbers can be edited directly in the field.
Note on format: Phone numbers must be entered in international format (e.g. +41 79 123 45 67). If the format is not followed, an error message appears directly below the field with an example of the correct format, and the number cannot be saved until it has been corrected.
Additional email addresses
The Additional email addresses section lets you store further email addresses for a resident, in addition to the active email address (shown at the top of the detail page under Active E-mail).
Additional email addresses improve the assignment of incoming requests: if a person writes from a private or work address to a public intake channel (omnichannel-to-ticket), the incoming ticket can be automatically assigned to the right person thanks to the stored address.
Add an email address
- Click Add new e-mail address.
- In the Type field, choose a category: Private, Work, or Other.
- Enter the E-mail address.
- Confirm with Add or cancel with Cancel.
Validation: Only valid email addresses can be saved. If the format is invalid, the message "Please enter a valid e-mail address" appears. An address that has already been stored cannot be added a second time.
Edit or delete an email address
- pencil icon next to an entry: edit an address.
- trash icon: delete an address.
Additional email addresses can be edited and deleted both by team members in Cockpit and by the residents themselves (in the app's profile settings). Changes are immediately visible on both sides.
What additional email addresses are used for — and what they are not:
- Assigning requests: if a person writes from a stored address to a public intake channel (omnichannel-to-ticket), the ticket is automatically assigned to the right person.
- No notifications: no emails — neither summaries nor notifications (e.g. about pinboard posts or comments) — are sent to additional addresses. The person only receives these at their active email address.
- No login: logging in to the app is not possible with additional addresses. Login is still done exclusively via the active email address.
External ID (ERP)
The External ID (ERP) field shows the ID from the connected ERP system for this person. If no ID is stored for this person — whether because no ERP integration is active, or because no ID was transferred for this person despite an active integration — the entire section is hidden, without any placeholder text. Not available is only displayed when multiple ERP data sources exist for the person — regardless of whether their values match — and only for team members whose own company itself has multiple ERP data sources connected. This field is read-only and is populated exclusively through the ERP integration.
Language
The Language field shows the person's preferred language and can be changed directly here. This setting controls the language in which the person receives notifications and messages from the app.
E-mail notifications
The E-mail notifications field shows the currently configured frequency at which the person receives email summaries, and can be changed directly here: daily, weekly, or never.