The supported form experience is for authenticated members. Treat the form as a reviewed information request with a defined audience and retention plan, rather than an unrestricted public form builder. A submitted response is evidence for review, not permission to modify other records.
Step 01
Define the smallest useful form
Use the supported text, long-text, boolean and single-select fields with permitted conditions. Review both language variants and publish an immutable version. Avoid collecting details that do not support the stated member-service purpose. Attachments and respondent drafts are outside this form slice.
Step 02
Test ordinary and sensitive review
Submit a controlled response with a member account. Verify which review group can see ordinary answers and which separately scoped group can see sensitive answers. Test export permissions and retention rather than assuming every reviewer can download the full response set.
Step 03
Review before routing into a case
Where the exact form version has an approved Case intake binding, inspect the response and approve the supported hand-off. Confirm the resulting case type and source link. Do not infer anonymous intake, employer forms, arbitrary workflow scripting or automatic changes to People records.