Forms
Forms collect the information needed when someone submits a request. Each service offering can have its own form with custom fields, so you gather exactly the right details for each type of request.
What Are Forms?
A form is a set of fields that a requester fills out when submitting a request. For example, a "Bug Report" offering might have a form with fields for the bug description, steps to reproduce, severity, and a screenshot upload. A "New Employee Onboarding" form might ask for the employee's name, start date, department, and equipment needs.
Forms in Nembl are standalone, reusable entities. This means you can create a form once and attach it to multiple service offerings. If your "Hardware Request" and "Software Request" offerings both need the same basic information, they can share the same form.
Creating a Form
- Go to Admin > Forms in the sidebar.
- Click New Form.
- Give the form a name (for example, "Bug Report Intake" or "Equipment Request Form").
- Start adding fields using the form builder.
Available Field Types
Nembl supports a range of field types to capture different kinds of information:
| Field Type | Use It For |
|---|---|
| Text | Short answers like names, titles, or brief descriptions |
| Text Area | Longer responses like detailed descriptions or instructions |
| Select | A dropdown list where the requester picks one option |
| Multi-Select | A list where the requester can pick multiple options |
| Checkbox | A yes/no toggle, such as "I agree to the terms" |
| Number | Numeric values like quantities or budget amounts |
| Date | Calendar date picker for deadlines or start dates |
| File Upload | Attachments like screenshots, documents, or spreadsheets |
Adding Fields to a Form
- In the form builder, click Add Field.
- Choose the field type from the list.
- Configure the field:
- Label — The question or prompt shown to the requester (for example, "Describe the issue").
- Help text — Optional guidance that appears below the field to clarify what is expected.
- Required — Toggle this on if the requester must fill in this field before submitting.
- Options — For Select and Multi-Select fields, add the available choices.
- Drag fields up or down to set the order they appear on the form.
Tips for Good Forms
- Keep forms short. Only ask for information you actually need to process the request. Long forms discourage people from submitting requests.
- Use required fields sparingly. Mark a field as required only if you truly cannot process the request without it.
- Write clear labels. Use plain language and be specific. "What software do you need?" is better than "Software."
- Add help text. A brief note like "Include the version number if known" can save back-and-forth later.
- Use the right field type. A Select field with predefined options is easier for requesters than a free-text field where they have to guess what to enter.
Attaching Forms to Offerings
Once your form is ready, attach it to one or more service offerings:
- Go to Admin > Services and open the service.
- Click the Offerings tab and open the offering you want to add the form to.
- In the Form section, click Attach Form and select your form.
- Click Save.
When someone submits a request for that offering, they will see your form and fill in the fields you defined.
Editing Forms
You can edit a form at any time by going to Admin > Forms and clicking on it. Changes to a form take effect immediately for new requests. Requests that have already been submitted keep the information that was entered at the time.
Reusing Forms
Because forms are standalone entities, you can attach the same form to multiple offerings across different services. This is useful when several offerings need the same basic information. If you update the shared form, the changes apply everywhere it is used.
Next Steps
- Publish your service to make it available for requests. See Publishing.
- Build a workflow to automate what happens after a request is submitted. See Workflow Builder.