Internal Fields
Internal fields are fields that only the team can see and edit. Applicants never see them; they do not appear on the portal form.
What they are for
Internal fields are useful for tracking information that the team manages internally, such as:
- An internal reference number or ID
- A reviewer’s notes or score
- An internal category or tag
- A decision date
- An approved amount
How they work
Internal fields appear in the application detail view, in the Additional fields section of the side panel next to the applicant’s submitted answers. The team can edit them at any time; changes are saved as a new revision with Save Application.
Internal field values can be used in email templates, for example with the {internalField.fieldId} variable. Date fields can also serve as the basis for the On Date Reached trigger in automations.
Available field types
Internal fields support nearly all the same types as regular form fields:
| Type | Description |
|---|---|
| Short text | Single-line text input |
| Long text | Multi-line text input |
| Number | Integer or decimal, optionally with a currency prefix (e.g. CHF) |
| Date | Calendar date picker |
| Select | Dropdown, one option |
| Multi-select | Dropdown, multiple options |
| Checkbox | Tick multiple options |
| Radio | One option only, optionally with an «Other» free-text option |
| Yes/No | Toggle for a yes/no answer |
| Heading | Bold section title within the side panel |
| Info text | Explanatory text between fields |
File uploads and repeater groups are not available for internal fields.
Visibility within the team
By default, internal fields are visible only to Owners. To also show a field to Members and Users, it is marked as public within the team when it is set up.
| Role | Default | Marked as public |
|---|---|---|
| Owner | ✅ | ✅ |
| Member | ❌ | ✅ |
| User | ❌ | ✅ |
Computed fields
An internal field can derive its value automatically from other fields, using a template with placeholders like {fieldId}.
Example: A summary template such as Application by {applicant-fullname}, CHF {budget-amount} fills the field automatically and updates live as other fields change.
Computed fields are read-only; they cannot be edited manually.
Conditional visibility
An internal field can be shown or hidden based on the value of another field. For example, a «Reason for rejection» field appears only when a select field is set to «Rejected».
The condition can reference any other field, both regular form fields and other internal fields. Like the rest of the internal field configuration, the Fundament team sets it up on request.
Multi-language support
Labels, descriptions and select options can be translated per language (German, French, Italian, English). Team members will see the fields in their preferred language.
Showing in the application list
Internal fields can be displayed as optional columns in the application list. Number fields with a currency prefix are formatted accordingly (e.g. CHF 12'500).
Adding internal fields
The app does not yet have an interface for creating internal fields. Like the rest of the form structure, internal fields are set up by the Fundament team; see Building Forms. To request them, describe each field with its type, label, options, visibility (Owners only or the whole team), and any conditions.