Set form access and publish
Separate public applications from forms that edit a specific customer’s record.
After this taskRestricted access does not create a submission.
Starting conditions and inputs
Complete field validation and choose public or restricted access.
Values for this task
entry_url, form_id, access_mode, allowed_identity, denied_identity, form_url, test_answer
Command sequence
open "$entry_url" && snapshot -i
click "$form_row" && snapshot -i
get text body
# Outside browser: The publisher confirms audience and link. Prepare separate allowed and denied test sessions.
open "$form_url" && snapshot -i
fill "$answer_input" "$test_answer" && snapshot -i
click "$submit_form" && snapshot -i
get text body
# Outside browser: Switch to the denied account or signed-out session.
open "$form_url" && snapshot -i
get text bodyRef targets and expected results
| # | Command / ref | Target and verification |
|---|---|---|
| 1 | click $form_row | Form record to publish |
| 2 | get text | Read form access mode and scope. |
| 3 | Outside browser | The publisher confirms audience and link. Prepare separate allowed and denied test sessions. |
| 4 | open | Form URL in the allowed test session |
| 5 | fill $answer_input | Input required for the test submission |
| 6 | click $submit_form | Test form submit button |
| 7 | get text | Read this submission acknowledgment identifier. |
| 8 | Outside browser | Switch to the denied account or signed-out session. |
| 9 | open | The same form URL |
| 10 | get text | Read the access-denial result. |
Check the result
Restricted access does not create a submission.
Resuming after interruption
Read the same IDs again. Preserve correct settings and update only differences.
Choose public or token access
Separate public applications from forms that edit a specific customer’s record. update_target requires token access. Customer login and messaging-account connections are separate features.
Publish the form
Enter an organization-unique slug, localized title, description, and success message. Activate the form and connect the intended website action. Share secure links only with their intended recipient, not on public pages.
Test allowed access
Submit the public form from a signed-out test browser. Open a secure form as its intended customer and check that it edits only the linked reservation. Verify source records after the success message.
Test denied access
Check rejection for invalid links, wrong targets, and unauthorized users. Disabling a form restricts new access while preserving existing submissions. Test allowed and denied paths before distributing the operating link.