New Employees & Master Data Form
Registration, approval, default employment type and custom fields in the master data form.
Two settings pages together determine how new employees enter your organisation and what data they leave behind: Einstellungen › Neue Mitarbeiter and Einstellungen › Stammdatenformular.
Neue Mitarbeiter — new employees
Konfiguriere, wie neue Mitarbeiter registriert, freigeschaltet und abgerechnet werden.
Freischaltung erforderlich — approval required
The page's central switch. When active, new users must be approved by an admin after registering before they can use the platform.
Because the setting fundamentally changes how new users experience the employee app, EVENTRA confirms in both directions:
Enabling approval
New users can log in and enter their data after registering, but have no access to events, applications or shifts until an admin approves them.
Disabling approval
New users get full access immediately after registering. Users already waiting stay inactive and still have to be approved manually -- switching this off does not let them in automatically.
Waiting users are reached via the Warteliste button on the Mitarbeiter page; it carries the number of open registrations as a counter. There you approve individually or in bulk -- the Datenstatus column shows beforehand whether their master data is Vollständig, Teilweise or Unvollständig.
Standard-Abrechnungsart — default employment type
The Personengruppenschlüssel assigned automatically to new employees -- whether they are invited or register themselves. It can be changed per employee at any time.
Why this matters
The employment type decides later whether somebody shows up in the minijob evaluation, in the 70-day rule, or in neither. A wrong default only surfaces at the monthly close.
Stammdatenformular — master data form
Definieren Sie zusätzliche Felder, die Mitarbeitende bei der Registrierung ausfüllen müssen.
Alongside the fixed master data (name, address, bank details etc.) you capture your own fields here -- T-shirt size, driving licence class, dietary requirements or whatever else your planning needs.
Fields and sections
- Feld hinzufügen creates a single form field.
- Abschnitt hinzufügen creates a heading to group fields under; Feld in diesen Abschnitt hinzufügen places a field directly beneath it.
- The Breite (width) setting decides whether a field takes the full or half form width -- so short fields sit side by side.
With nothing created yet: "Noch keine Felder vorhanden".
Deleting
Deleting a field
"Bereits erfasste Daten für dieses Feld bleiben erhalten, werden aber nicht mehr angezeigt." A deleted field removes no history -- it only hides it.
Deleting a section
"Die enthaltenen Felder bleiben erhalten und rücken in den vorherigen Abschnitt." A section is a pure heading; deleting it costs no fields.
Where the same builder shows up
The form builder is used in several places, each under its own name:
| Context | Where the form appears |
|---|---|
| Onboarding | During registration and in the master data wizard |
| Bewerbung | As an additional step in the application wizard -- the fields can react to the selected tasks |
| Akkreditierung | As part of the security clearance process |
Document keys
Fields can carry their own document key under which uploaded files are stored. Only lowercase letters, digits and underscores are allowed, and the key must start with a letter. The form feld1 is reserved -- those keys are assigned by the system.