# A separate FAQ per module: questions about that product line only — MijnEvent

  [Home](https://mijnevent.nl/en) / [Blog for event organizers](https://mijnevent.nl/en/blog) / A separate FAQ per module: questions about that product line only   faq modules dashboard 

# A separate FAQ per module: questions about that product line only

Every module has its own 'Frequently asked questions' tab with its own switch. On an event, the module questions you have switched on appear alongside your organisation-wide questions.

 [Jasper Koers](https://mijnevent.nl/en/author/jasper-koers) · 16 July 2026 · 5 min read 

       In short

- Every module has a 'Frequently asked questions' tab headed 'Frequently asked questions for this module'.
- Every module has its own 'Show FAQ on the public page' switch — the one for your organisation does not apply here.
- 'Add default questions' gives you questions per module that are specifically about that product line.
- On an event, the event, module and organisation questions are merged; only the scopes you have switched on are counted.

  Your organisation-wide FAQ answers the questions that come back at every event: how do I get my ticket, how do I pay, what if it does not arrive. But as soon as you use a module, a second kind of question turns up — one that is only about *that* product line. How do I order at the food truck? Do I get my deposit back? What happens if the group is full?

That is why **every module has its own FAQ**, separate from your organisation's.

# Where it sits

Two routes lead there.

The first: open the module in your dashboard and choose the **"Frequently asked questions"** tab. For Food trucks it sits next to the tabs for trucks, kitchen and email texts; for Rentals, Shop, Memberships, Courses, Cashless, City card and Donations it works exactly the same way.

The second: go to **Modules** and click the small **"Frequently asked questions →"** link underneath the card of an active module. That opens the same admin screen on a page of its own, with a **"Back to the modules overview"** link at the bottom.

What you get is the same FAQ manager as [at organisation level](/en/blog/setting-up-your-own-faq), but with the heading **"Frequently asked questions for this module"**.

# A separate switch per module

This is the point where people get caught out: the **"Show FAQ on the public page"** switch is **per scope**. The switch you turned on for your organisation does nothing here. Every module has its own button, and — as everywhere — it is **off by default**, with the same warning underneath it: *"While this is off, visitors see nothing — even if questions are ready and waiting."*

That sounds long-winded, but it gives you precise control. You can publish the food truck questions and hold back the rental ones a little longer, until your range is final.

# The quickest start: default questions

Just as with your organisation FAQ, there is an **"Add default questions"** button. The difference is in the content: for a module those questions do not come from the general ticket set, but from the platform's module register — so they are specifically about *that* product line.

For Food trucks & mobile catering, for instance, you get questions about how visitors order (by QR on their phone, or simply at the counter through the truck's register screen, with the same queue numbers and the same kitchen display), whether every operator gets access to your dashboard, and where the revenue lands. For Rentals it is about the deposit and where the booking money ends up; for Courses about what happens when a group is full and how you keep track of attendance.

Do run through them before you publish, though. Some default questions also answer what the module costs *you* as the organiser — useful to know, but usually not something your visitor needs to read on your public page. Every question you add can simply be edited, or set to **Inactive** with a single click.

# Editing, reordering, on or off per question

The rest works identically to the organisation FAQ. Every question shows an origin badge (**Manual**, **AI**, **Website** or **Default**), has up and down arrows for the order, and a button to set it individually to **Active** or **Inactive**. **Edit** and **Delete** sit next to those.

The AI buttons are there too: **"Generate FAQs"** suggests questions based on what MijnEvent knows about *this* module, and **"Generate from a URL"** reads exactly one page of your own site. Suggestions always land in the **Suggestions** dialogue first — *"Choose which questions you want to add. You can still edit them afterwards."* — and you accept them per question or via **"Add all"**.

# The inheritance: how it comes together on an event

This is where it gets interesting. An event has its own FAQ tab as well, and on that tab sits the sentence that sums up the whole architecture:

> *"An event also inherits the module and organisation questions you have switched on."*

When it assembles the public FAQ of an event, MijnEvent merges three layers, in this order:

1. **The event's own questions** — the most specific, so at the top.
2. **The questions from the modules you have switched on** — only from modules that are active for your organisation *and* whose module switch is on.
3. **Your organisation-wide questions** — the general foundation, at the bottom.

Three rules guard the outcome. Only scopes that are **switched on** count: if a module's switch is off, that module contributes nothing, even if questions are ready and waiting. Only **active** questions come along. And **duplicate questions are filtered out** — if the same question exists at several levels, the most specific one wins.

In practice that means: write your general answers once at organisation level, put the questions that only apply there on each module, and use the event FAQ purely for what genuinely differs per event. You never have to repeat anything.

# How to switch it on

1. Open the module in your dashboard and choose the **"Frequently asked questions"** tab — or click **"Frequently asked questions →"** underneath the card in **Modules**.
2. Click **"Add default questions"** and adjust the answers to your situation.
3. Set questions your visitor does not need to **Inactive**.
4. Turn on the **"Show FAQ on the public page"** switch for *this* module.
5. Check an event page: there you will see the module questions alongside your organisation-wide ones.

   Frequently asked questions

## Frequently asked questions

## Where do I find a module's FAQ?

 There are two routes: open the module in your dashboard and choose the 'Frequently asked questions' tab, or click the 'Frequently asked questions →' link underneath that module's card in the modules overview.

## Does my organisation's switch also cover the module FAQ?

 No. Every scope has its own 'Show FAQ on the public page' switch, and everywhere it is off by default.

## What exactly does an event inherit?

 The event's own questions, plus the questions from the modules you have switched on, plus your organisation-wide questions. Only scopes whose switch is on are counted; duplicate questions are filtered out.

## Are the module default questions the same as the organisation-wide ones?

 No. Organisation-wide default questions are about tickets, payment and admission; module default questions come from the module register and are about that specific product line.

  [    Back to blog ](https://mijnevent.nl/en/blog) 

  MijnEvent

## Read more

 [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/automatic-membership-renewal-dutch-law.webp) memberships 

 Jasper Koers · 27 July 2026 · 6 min read

## Automatic membership renewal: collecting fees within Dutch renewal law

Automatic renewal saves your club a pile of chasing work, but the law has rules about cancelling. Here is how renewal works in MijnEvent, and how to keep it clean.

 ](https://mijnevent.nl/en/blog/automatic-membership-renewal-dutch-law) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/ontruimingsverslag-evenement-bewijsstuk.webp) safety 

 MijnEvent · 27 July 2026 · 5 min read

## The evacuation record: why the day after your event matters for the next permit

An evacuation — real or drilled — is only finished once it is on paper. What belongs in an evacuation record, why the municipality asks for it, and how to make the record write itself instead of reconstructing it afterwards?

 ](https://mijnevent.nl/en/blog/evacuation-record-event-evidence) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/knmi-weeralerts-veiligheidsplan.webp) safety 

 MijnEvent · 27 July 2026 · 3 min read

## Weather monitoring in your safety plan: how KNMI warnings land in your alerts and logbook automatically

Almost every safety-plan format has a 'weather monitoring' section — and almost nobody fills it in concretely. The Safety & Permit module pulls the KNMI warning code for your event location every hour and turns it into a demonstrable process.

 ](https://mijnevent.nl/en/blog/knmi-weather-alerts-event-safety-plan) 

   MijnEvent

## Ready to get started?

Create a free account and sell your first tickets today.

 [Start free](https://mijnevent.nl/registreer) [Pricing](https://mijnevent.nl/en/pricing)