Use the Contracts tab in Organization management to define how new contracts behave for an organization unit. These settings are inherited by lower-level organization units unless you override them on a child unit.
Contract settings are mainly used for two purposes:
Defaults fill in common values automatically when a user creates a new contract.
Enforcement makes selected values mandatory, so users cannot save a contract that conflicts with the organization policy.
Where to find the settings
Open LivionKey Register.
Go to Organization.
Select the organization unit you want to configure.
Open the Contracts tab.
If a setting is inherited from a parent organization unit, the tab shows an inherited-value message. Click Update or Edit in the relevant section to save local settings for the selected unit.
Contract settings
The Contract settings section controls defaults and enforcement for new contracts.
Validity
Default start time defines the start time used when a new contract is created.
Contract creation time: the contract starts from the time it is created.
Custom default start time: the contract form opens with the configured time.
Contract validity defines the default end of the contract.
Permanent: no end time is set by default.
Fixed end time: the contract ends at a configured time.
Duration from start time: the end time is calculated from the start using days, hours, and minutes.
Access Schedule controls whether access schedules are enabled by default for contracts. When enabled, the contract can limit access to selected time windows inside the contract period.
Contact
Contact lookup type controls how the main contact is found when creating a contract.
Manual: the user triggers contact lookup manually.
Auto: the system searches for matching contacts automatically while the user types.
Default phone prefix pre-fills the phone number prefix when the contact phone field is empty, for example +358.
Main contact email required makes a valid email address mandatory for the main contact.
Main contact mobile required makes a mobile phone number mandatory for the main contact.
Notifications
Email and SMS notification defaults define whether the main contact should receive contract notifications by default.
Each channel also has an enforcement option:
If enforcement is disabled, the default is only a starting value and the user can change it.
If enforcement is enabled, the selected default state is locked.
This means notification enforcement can require a channel to stay enabled or require it to stay disabled, depending on the default selected for that channel.
If email notifications are enforced as enabled, the main contact must have a valid email address. If SMS notifications are enforced as enabled, the main contact must have a phone number.
Verification
Verification type defines the default verification method for the contract.
Available options can include:
No verification
Signature via tablet or phone
Strong Authentication, when the feature is available for the organization
When verification enforcement is enabled, the selected verification type becomes mandatory. The contract cannot be saved with another verification type.
Contract creation optional fields
This section controls whether optional fields are shown in the contract creation form.
Contract ID: show or hide the Contract ID field.
Pincode: show or hide the Pincode field.
Hidden fields are not shown to users when they create a new contract.
Contract instructions
Contract instructions are informational notes shown to managers during contract operations.
You can add separate instructions for:
Handover instructions
Receive or return instructions
Instructions can include a title, rich text content, and priority. They are inherited from parent organization units and are shown read-only when inherited.
Instructions do not block users from completing an operation. Use Required Checks when a step must be confirmed before completion.
Required checks
Required checks are mandatory confirmations that block completion until the manager completes them.
Each check can include:
A label
An optional description
One or more applicable operations
Supported operations are:
Mechanical key handover
Mechanical key receive
Mechanical key return
iLOQ S5 key handover
iLOQ S5 key return
When a required check applies to an operation, the manager must complete it before the operation can be finalized. Completed checks are recorded in the contract audit trail.
Required checks are inherited from parent organization units. Inherited checks are displayed separately so users can see where they come from.