These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Form Builder Platform
- Who it's for
- Multi-organization programs
Multi-organization programs
Programs with several organizations need clarity about who owns a field policy and a form definition. Organizations connect to People, Field Definitions and Form Definitions. A Form Owner can tie a form revision to its owning organization, while the reviewer records a decision against the exact source revision. Source Mappings describe how named external fields map to the form policy when a connection is set up.
How Form Builder Platform is set up for you
Ownership
Give each form definition an organization and a named owner.
Field policy
Keep a code and effective period on the field definition so another form owner can find the intended policy.
Mapped data
Review the source and target field names and transform rule before using a source mapping.
Programs with several organizations need clarity about who owns a field policy and a form definition. Organizations connect to People, Field Definitions and Form Definitions. A Form Owner can tie a form revision to its owning organization, while the reviewer records a decision against the exact source revision. Source Mappings describe how named external fields map to the form policy when a connection is set up.
Begin with one organization, its People records and a single form. Agree on the field policy and its effective dates, then create a definition with a schema version. If an external source feeds a field, document its source field, target field and transform rule. Run a submitted line through review and confirm its parent form belongs to the expected organization.
After the first case, repeat it with another organization. The owner should be able to explain which policy applied, which reviewer decided and which operator handled the resulting action. Review access with actual users before release, especially for evidence attachments and returned decisions.
Features to start with
Roles on the team
- Admin
- Maintains organizational access and the people who own form work.
- Form Owner
- Owns the definition, field policy and publication handoff for a form revision.
- Operator
- Works on submissions and records the result of a validated action.
- Independent Reviewer
- Decides whether a source revision and its submitted lines can proceed.
- Evidence Verifier
- Checks supporting documents and records who verified them.
Set up Form Builder Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.