Purposes
The guardrail that decides which Salesforce fields and flows a form may touch.
A Purpose is an administrator-approved permission to use specific Salesforce fields and flows. It is the product's central guardrail, and the reason a marketeer cannot quietly point a public form at a sensitive field.
How it fits together
Purpose "Lead Capture"
├── Purpose Field Lead.FirstName read + edit
├── Purpose Field Lead.Email read + edit
├── Purpose Field Lead.Rating read
└── Flow Send_Welcome_Email (whitelisted, with its variables)
Form "contact-us-1"
└── Form Purpose ──► Purpose "Lead Capture"
An administrator builds the purpose. A marketeer assigns it to a form. The form can then use exactly those fields, in exactly those directions:
- Read access lets a field be prefilled from Salesforce (Data Mapping).
- Edit access lets an action write to it (Submission Actions).
- A whitelisted flow can be invoked by a submit action.
A field with neither box ticked is not in the purpose at all.
Why you will meet it
You will run into purposes in three places, and it is always the same cause:
- Data Mapping offers no source objects → no purpose grants read access.
- Submission Actions offers no objects or fields to write → no purpose grants edit access.
- Invoke flow shows no flows → no purpose whitelists any.
In each case the fix is the same: an administrator adds it to a purpose, then you assign that purpose to your form. See Assign purposes.
It is enforced on save
This is the part that matters. The pickers hiding a field is a convenience; the real enforcement is at Save.
If a submission action writes a field, or a data mapping reads a field, that the form's assigned purposes do not grant, Save is rejected with a message naming the field. You can type an API name by hand into an unsaved form, but you cannot save it.
A form with no purposes assigned cannot save any Salesforce field reference at all.
This is a server-side check, so it holds regardless of what the interface allowed you to type.
Who creates them
Administrators, in the Purpose Manager in the Flux Forms Setup app. See Purpose Manager.
