# Configure suggestion submission fields > Add optional fields to a suggestion setup Add a custom form when members need to provide more than the default suggestion and details. The form belongs to one suggestion setup. Existing setups keep their current form until you enable a custom one. ## Configure it in the dashboard 1. Open your server in the [dashboard](/docs/dashboard) and choose **Suggestion setup**. 2. Select a setup, then open **Submission form**. 3. Turn on **Use a custom submission form**. The editor starts with a required **Title** field and a required **Details** field. You can add, edit, remove or reorder fields. 4. For each field, set its label, whether members must fill it in, its maximum character count and its display format. 5. Choose **Save setup**. Fields appear in the order shown in the editor. You can add up to four fields, and at least one must be required. The configured maximum content, including headings and spacing, must fit within 1,800 characters. Display formats are **Normal text**, **Heading 1**, **Heading 2** and **Heading 3**. These are the three heading levels Discord supports. Heading formats add the matching Markdown heading prefix to the submitted value. You can select one field as the discussion thread title. It must allow no more than 40 characters. Aethor names the thread `[#13] More community events discussion`, using the submitted title. If the title is blank, Aethor uses the usual thread name. With **Auto thread** enabled, the thread starts when the suggestion is published. Otherwise, the saved title is used when a member starts a thread from the suggestion card's configured discussion button. Selecting a title field does not enable either thread mode. Changing the form affects future modal submissions. Queued submissions keep the form used when submitted. Editing a published suggestion still edits its message text; it does not change the saved discussion title or rename an existing thread. Later setup changes do not reformat existing suggestions. For example, a **Heading 1** Title value and a normal Details value appear on the suggestion like this: Suggestion #13

More community events


Host a monthly community night. The suggestion text stores `# More community events` followed by `Host a monthly community night.` The heading and spacing count toward the 1,800-character total. ## Configure it in Discord Run `/setup submission-form` and choose the suggestion setup. The private editor lets you enable or disable the form, add a field, select a field to edit, remove or move it, and choose or clear the discussion-title field. Enabling the form starts with required **Title** and **Details** fields. Select a field and use **Move up** or **Move down** to change its position. The preview shows the current draft. Choose **Save form** to apply it, **Continue editing** to return to editing, or **Discard draft** to cancel. The Discord editor uses the same field limits and format choices as the dashboard. It saves changes to the setup, so either editor shows the same configuration. If validation fails, correct the reported field limit or required-field setting before saving. Drafts expire after 30 minutes. If a draft expires or someone changes the setup while you are editing, reopen `/setup submission-form` to load the current configuration. ## What members see With a custom form enabled, `/suggest` and the setup's submission button show its configured fields. Members still submit through the normal suggestion workflow, including the review queue and attachment handling. Typing a regular message in the suggestions channel keeps the existing message-submission behavior. For the full member workflow, read [Submit and follow suggestions](/docs/suggestions/suggesting). To configure a persistent button, read [Create a suggestion submission panel](/docs/suggestions/submission-panel).