Forms

Forms collect structured input from inside or outside the company and can trigger one or more downstream workflows.

Building a form

• Use the builder to add fields (text, paragraph, email, number, dropdown, checkbox, date, file).
• Or Build with AI (AI Studio → Build with AI): describe the form in plain language and the assistant drafts the fields live, asks what should happen on submit, and can even build the workflow it triggers. See AI Studio.
• Set access: Internal (signed-in), Public (anyone with the link), Protected (access code), or Anonymous (no identity stored).
• Scope to a department and set a retention policy.

Triggers (On submit)

A form can fire multiple actions on submission — chain as many as you need:

• Open a ticket — optionally into a specific queue/type.
• Start a project — launch a blueprint as a run; tasks auto-route to assignees.
• Notify people — alert specific members.

Example: an IT Request form opens an IT ticket and starts an onboarding project to track the work — from a single submission.

Tracking submissions

• Submitters can open My submissions (Forms → My submissions) to see everything they've sent and its live status, pulled from any tickets or projects each submission created.

Roles

• Submit: anyone with access (including public/anonymous, per form settings).
• Build / manage: form.manage (managers and above).