Custom Fields
Information that does not fit into a standard field gets its own field. Custom fields are available for security officers, sites and orders.
Requirements
- Owner role
Creating a field
Settings, Custom fields section. First select the entity type: Security officers, Sites or Orders. Each has its own list.
A new field requires a label (the text shown in the form) and a technical key (such as kundennummer). The available types are Text, Number, Date, Selection and Switch. A selection requires at least one option.
The type and key are fixed after creation and can no longer be changed. For selection fields, only new options can be added later. Existing options remain unchanged. It is better to consider this briefly than to create a second field afterward.
In the form
Created fields appear in the relevant record under the heading "Tenant-specific information for this record", in the order you define here. Use the arrows to move each field up or down.
Deactivate instead of deleting
A field that already contains values cannot be deleted. The message states this and suggests Deactivate.
A deactivated field disappears from the forms, but previously recorded values are retained. This is the correct approach when information is no longer needed but the history must remain accurate.
Related
- Team and RolesSix roles, with a finely structured set of permissions above them. What someone sees is determined by the permission, not the role alone.
- Orders and SitesThe order generates the shifts. The site provides the geofence, contacts and prices.
- Settings GuideThe settings are organized by topic, with the navigation on the left. This chapter explains what each section contains and where to find details.
Updated on: 03.09.2026