This guide provides a step-by-step approach to correctly fill the ModuleSettings table. This table is used to configure the behavior, display, and functionality of each survey module.

The table is linked to the fw\_modules table via moduleid, allowing different survey modules to have their own configuration settings.

You can find the detailed structure of the ModuleSettings table here:
👉 Module Settings Table Structure

The id column is the primary key and uniquely identifies each module setting record.

Input:

- Automatically generated (AUTO\_INCREMENT) - No manual entry is required.

Example:

✅ Notes:\ 💡 This field acts as the unique identifier for each module setting.

This field links the setting to a specific module in the fw\_modules table.

Input:

- Enter the id of the module from the fw\_modules table. - The moduleid must already exist in fw\_modules.

Example:

✅ Notes:\ 💡 Without this, the module will not recognize the settings.

This field defines whether the module is continuous or wave-based.

Input:

- `continuous` → Ongoing survey without time restriction. - `wave` → Survey conducted periodically.

Example:

✅ Notes:\ 💡 If you select `wave`, make sure to configure wave schedules.

Defines how the survey will appear to respondents.

Input:

- `singlepage` → All questions on one page. - `default` → One question per page.

Example:

✅ Notes: 💡 `singlepage` can increase survey abandonment rates.

Defines how long an invitation remains valid.

Input:

Integer value (number of days before an invitation is discarded).

Example:

✅ Notes: 💡 Set a reasonable expiry to avoid outdated feedback.

Controls the email layout.

Input:

`logoontop` → Logo at the top of the email.
`logoonside` → Logo on the side of the email.

Example:

✅ Notes:\ 💡 Choose a layout matching your brand guidelines.