Field bindings
Bindings stamp values from outside the case (today's date, or your company profile) onto generated output at fill time; they resolve at generation and are never stored in case data. Values that arrived with the file are not bindings: those are delivery inputs.
Values on a generated document come from four places. They come from the document itself (Extracted) or the person running it (Form field). They can arrive with the file (From the delivery) or calculate via formula (Computed).
Bindings handle the remaining values. They stamp an outside context onto the page. A binding is one of four derived-output kinds a field can carry. You set it up with a template open in the editor.
System bindings
The System source exposes the current date and time. It synthesizes a fresh value on every generation. A date field stamps the day you actually generate the document. You regenerate the file next week, and the new PDF carries next week's date.
You enter a time synonym in the Path field. Document Blueprint recognizes today, todaysDate, todays_date, date, currentDate, and current_date for the current day. It recognizes now, timestamp, and currentTime for a full timestamp.
Case does not matter, and the app ignores a leading system. prefix. A binding output with its Type set to Date falls back to today's date even without a recognized path.
Company profile bindings
The Company profile source reflects current workspace settings. Workspace owners edit this profile under Settings > Company. You update your address once. Every future generation across every template uses the new address.
The app matches the field against your profile. Editor fields do not match these profile entries. A company profile binding on an editor field produces an empty stamp.
The binding ignores the Path field. These bindings also resolve to nothing during portal signing. They resolve to nothing when using AI document tools.
Setting up a binding
You apply a binding to a field. A static input overrides a binding. The app skips the binding when the input source is Static.
The new output defaults to an AI instruction kind. You must change the Kind to Binding before the source controls appear. This pre-selects the System option as the Source. Changing the Kind again clears your source and path choices.
You must ignore the Path placeholder. It suggests email examples that return empty stamps. Once you configure the binding, the field list subtitle updates to system or company.
Bindings live outside case data
Binding values resolve at read time. The app looks up the current value at generation. It stamps this value through the output's Write zones. The value is never saved back to the case data.
These values appear on the generated document. They show as a non-editable row on the template editor's Data tab. They do not appear in the case ledger. You cannot sort, filter, or share a bound value as a case field.
File delivery values require an input
Emails and Google Drive folders carry delivery values. An email provides a subject line, a sender address, and a message body. A Drive automation provides a file name, a folder name, and two timestamps. You capture these with an input, not a binding.
Open the field and set Value source to From the delivery. Pick a target in the Delivery part menu. The app reads a delivery input as the file arrives. This happens before the case exists.
The delivery value can decide which case receives the file. The app saves the result onto the case like any other collected value. Bindings work on every case regardless of origin.
A case from a manual upload lacks a delivery envelope. Delivery inputs on that case stay empty.