Submissions

Collect, review, and process form responses with optional profile creation.

What Happens When a Form Is Submitted

When someone fills out and submits a form, Bosca performs several steps automatically:

Validation — All fields are checked against the form's validation rules. If anything is invalid, the user sees error messages and the submission is blocked until they fix the issues.
Storage — The validated data is securely stored as a submission record, linked to the form it came from.
Profile creation — If the form has profile mapping enabled and the submitter is anonymous, a user profile is created from the form data.
Task creation — If the form is a Work Ops form, a task is automatically created from the submission data.
Status tracking — The submission enters the lifecycle with a status of Pending, ready for your team to review.

Submission Statuses

Every submission has a status that tracks where it is in your processing workflow:

Status	Meaning
Pending	The submission has been received and is awaiting review or processing by your team
Processed	The submission has been handled and completed — for example, a Work Ops task was created, or the data was reviewed and acted upon
Archived	The submission has been stored for historical records and is no longer active
Rejected	The submission was reviewed and determined to be invalid or inappropriate
Spam	The submission was flagged as spam, either by rate limiting or content analysis

Viewing Submissions

You can review all submissions for a form directly in the form builder. Open your form in the builder and click the Submissions tab to see a list of all collected responses. Each entry shows the submitted data, the submission date, and the current status.

From the submissions view, you can review individual responses, update their status, and see any associated profile or task information.

Profile Mapping — Automatic Profile Creation

For public-facing forms, you often want to capture information about anonymous visitors without requiring them to create an account first. Profile mapping solves this by automatically creating a user profile from form data when an anonymous visitor submits the form.

Here is how it works:

In the form builder settings, you enable profile mapping for your form
You map form fields to profile attributes — for example, the "Full Name" field maps to the profile name, and the "Email" field maps to the profile email
When an anonymous visitor submits the form, Bosca creates a user profile populated with the mapped values
This profile can then be used for follow-up communication, audience segmentation, or any other workflow that needs contact information

Profile mapping only applies to anonymous submissions. When a logged-in user submits a form, the submission is automatically linked to their existing profile — the mapping configuration is skipped.

Rate Limiting

Public forms are protected against abuse with automatic rate limiting. Each IP address is limited to 10 submissions per minute. Submissions that exceed this limit are rejected and not stored. This prevents bots and bad actors from flooding your forms with junk data.

Rate limiting applies only to anonymous (unauthenticated) submissions. Logged-in users are not subject to rate limits.

Work Ops Integration — Forms That Create Tasks

Forms of type Work Ops automatically create tasks when submitted. This is ideal for workflows like bug reports, feature requests, support tickets, or any process where a form submission should kick off a trackable task.

When you configure a Work Ops form, you map form fields to task properties:

Project — Which Work Ops project the task is created in
Task type — The type of task (e.g., bug, feature request, support ticket)
Priority — The priority level for the task
Summary — The form field that becomes the task title
Description — The form field that becomes the task description
Assignee — Optionally assign the task to a specific team member
Dates — Optionally set start and due dates from form fields

After submission, the task is created automatically and the submission status moves to Processed. The submission retains a link to the created task for traceability.

Work Ops forms are a powerful way to turn external input into actionable work items. For example, a public bug report form can automatically create a bug task in your engineering project, assigned to the right team, with the correct priority — no manual data entry required.

For details on configuring Work Ops forms, see the Builder page. For how validation works before submission, see Validation.