Field builder
Configure typed request fields and validation.
Feature
Turn incoming requests into structured work from the start.
Publish an intake path, capture the fields the team needs, and route requests into the same workspace used to deliver them.
How it works
A clear operating path.
Configure the structure once, then use it where the work happens.
- 01
Build the fields
Configure the request fields and validation the team needs.
- 02
Complete the portal form
Collect a filled structured request in the portal.
- 03
Confirm the request
Return a clear submission confirmation, request key, and tracking actions.
Capabilities
What teams can use today.
These capabilities are implemented in the current TOW product.
Request catalog
Publish the available structured request types.
Portal requests
Give requesters a scoped list of request types, statuses, and update dates.
Submission confirmation
Return the request key and clear next actions as soon as intake completes.
Control point
AI follows the same boundary.
Where AI is enabled, accessible context and review-oriented flows apply to the surrounding workspace rather than bypassing its controls.
- Scoped context
- Configured provider
- Visible proposals
- Human decision
Deployment and security
Control the deployment and the boundary.
Use TOW Cloud, run TOW on controlled infrastructure, or operate an air-gapped Docker Compose deployment. Permissions, identity settings, exports, and AI provider choices stay visible to administrators.
Explore self-hosting
FAQ
Questions worth answering clearly.
Current product, deployment, and commercial boundaries.
Is field builder implemented in TOW?
Yes. Field builder, Request catalog, Portal requests, Submission confirmation are part of the current product surface and are backed by the linked implementation evidence.
Can this be self-hosted?
Yes. The capability is available within the TOW application in a configured self-hosted deployment.
See TOW in your environment