The PDF Forms editor controls the PDF Forms module - a universal tool that brings ready-made, fillable PDF documents (e.g. membership applications, registration forms, consent forms) into your app. You upload the PDF once, your app automatically detects the form fields inside it and builds a digital form from them. End users fill it out conveniently in the app - at the end, the original PDF is filled in on the server and sent as a file attachment by email to the configured recipients.
FormsUpload PDFs, let fields be detected, maintain labels in multiple languages, combine fields into groups, set required fields and order, configure recipients per form.
Fill modeChoose per form: a guided mobile form, or fill out the original PDF directly and interactively.
ViewList, grid or carousel - how the available forms are displayed in the frontend.
Recipients & Opt-InGlobal defaults for recipients and the double opt-in flow (email confirmation by code).
BehaviorMy submissions, archiving, GDPR retention, list limit, admin push, home section.
DesignAccent color and card radius of the form cards.
Many clubs, associations and organizations work with fixed PDF templates - membership declarations, donation forms, official applications. Instead of rebuilding these forms, you simply upload the finished PDF. Requirement: the PDF must be a true AcroForm PDF, meaning it already contains fillable form fields (text fields, checkboxes, choice lists).
In short, the flow looks like this:
The admin uploads a PDF. Your app reads the contained form fields on the server.
A digital form is created automatically from those fields. You refine it: translate labels, mark required fields, sort the order.
You configure the recipients (e.g. the club office) and decide whether the user receives a copy.
The end user picks the form, fills it out in the app and submits it.
The original PDF is filled in on the server with the entered values and sent as a file attachment by email.
You can offer as many forms in parallel as you like - each with its own recipients and its own settings.
Every uploaded PDF becomes a template. A template has a title, a description, its detected fields, the recipients and a few toggles (active/inactive, copy to user, opt-in). Templates are maintained by the admin and are available to all app users.
When a user fills out a form and submits it, a submission is created. It contains the entered values and (if archiving is enabled) the filled PDF. Users see their own submissions under “My submissions”, admins see all submissions in the admin area.
If double opt-in is enabled for a form, the application is not sent immediately. Instead, the user receives an email with a 6-digit code to enter in the app. Only after this confirmation is the PDF generated and sent. This ensures that the email address provided really belongs to the user.
The filled PDF is always sent as a file attachment in the email - both to the fixed admin recipients and to the optional user copy. Delivery runs through your app’s central email pipeline (Email module).
The PDF Forms module is activated with a single tap (activation type “configuration”) - no external credentials are required. The actual work (uploading PDFs, maintaining fields) is done afterwards in the editor.
Users open “Available forms” (/pdf-forms), pick a form, fill it out and submit it. Optionally they see “My submissions” with status. Forms can be shared via deep link and wired straight into the app navigation via the navigation target picker (“Forms” tab, see below).
Admin
Under /admin/pdf-forms you’ll find a dashboard with key figures (templates, submissions, pending, sent), the template management with search and filter, plus the submission overview.
Every PDF form you create can be placed directly into your app navigation - for instance as an entry in the bottom navigation bar, on a custom page or as a button. Wherever you pick a navigation target, there’s a dedicated “Forms” tab for this: it lists all active PDF forms to choose from. Pick one and your app automatically links to the matching fill-out page (/pdf-forms/fill/{id}).
This way you guide users with a single tap straight to the desired form - without the detour via the form overview.