Lock Policies Reference
Lock policies let you control when a field in a detail form becomes read-only. Once a lock is active, respondents can no longer change the field value.
What lock policies do
A lock policy freezes a field so that its submitted value cannot be modified. This is useful when downstream processes depend on a fixed answer -- for example locking an event date after a venue has been booked, or preventing product changes after an order confirmation.
Lock policies are configured per field in the builder's Lock Policies panel.
Configuration
Each lock policy has a main toggle and up to three independent lock rules. When more than one rule is active, the field locks as soon as any rule is met.
| Option | Values | Default | Effect |
|---|---|---|---|
| Enable lock policy | on / off | off | Master switch. When off, all rules are ignored |
| Lock | on / off | off | Immediately locked -- the field cannot be edited regardless of any other condition |
| Final decision | on / off | off | Lock the field once a non-empty value has been submitted |
Deadline types
In addition to Lock and Final decision, you can lock a field based on a point in time. There are two deadline modes.
Absolute deadline
Lock the field after a fixed date and time.
| Option | Values | Effect |
|---|---|---|
| Deadline mode | Fixed date | Use a fixed date and time |
| Date and time | e.g. 2026-06-15 10:00 | The exact moment the lock activates |
Relative deadline
Lock the field relative to the linked event's start or end date. This is the most common setup because it adapts automatically to every event.
| Option | Values | Effect |
|---|---|---|
| Deadline mode | Relative to event | Calculate the deadline from the event |
| Anchor | Event start / Event end | Reference point on the event |
| Days | Number | How many days before or after the anchor |
| Direction | Before / After | Direction of the offset |
Example: Lock the field 3 days before the event starts:
Deadline mode: Relative to event
Anchor: Event start
Days: 3
Direction: Before
Product lock policies
Product fields support an additional Lock scope setting that controls what exactly gets locked.
| Scope | Effect |
|---|---|
| Selection only | The selected products cannot be removed, but the quantity can still be increased |
| Selection + quantity | The product selection and all quantities are completely frozen |
All other lock rules (Lock, Final decision, Editable until) work the same way on product fields.
Fields that support lock policies
Lock policies can be configured on any field that collects user input. This includes:
- Basic fields -- text, text area, email, phone, number, date, time, checkbox, radio, dropdown, picture choice
- Contact fields -- salutation, first name, last name, company, phone, mobile, email
- Address fields -- street, postal code, city, address line 2, address line 3, country
- Event fields -- event title, event date, end date, start time, end time, attendees, days, contact, people min, people max
- Advanced fields -- file upload, rating, products, rooms, privacy/terms
Fields excluded from lock policies
The following field types are design or layout elements with no user-editable value. They cannot have a lock policy:
- Heading
- Text Block
- Alert
- Separator
- Spacer
- Image
- Rich Text
- Custom Data
- Cart Summary
- Assignee Block
- Summary Details