Skip to content

Municipal staff guide

The whole backoffice is at /staff, with your municipal user, in Catalan, Spanish or English.

  • Activities (summer camp, sports campus, music school…) with a name, description, season and, if needed, minimum and maximum age. Write descriptions in Catalan: for now they are not translated automatically.
  • Each activity has sessions with dates, price, places and the enrollment window (when it opens and closes). The public catalog shows free places and a countdown to opening; nobody can enroll before that time.
  • You can add places to a session at any time: if there is a waitlist, families are promoted automatically in order.
  • An activity or session that already has enrollments is not deleted: it is archived, and the history is kept.
  • Place allocation is concurrency-safe: even when many families click at once, each place is allocated exactly once, in first-come order with a timestamp.
  • When a session is full, requests join the ordered waitlist. You don’t manage it: when a place frees up (cancellation or more places), the first family automatically gets an email with a deadline to pay; if they don’t pay, the place goes to the next one. A periodic sweep guarantees promotion whenever a place is free.
  • To cancel an enrollment: session screen → cancel button. Waitlist promotion is automatic.
  • Discounts in the menu: a single queue with every pending document (residence certificates, large-family cards). The document is required.
  • Open the document and approve it or reject it with a reason. The family gets the email automatically. Who reviewed it, and when, is recorded.
  • If you reject before the family pays, the enrollment goes back to the full price. If they already paid, the difference is handled per your ordinance, outside the platform.
  • We configure the residence and large-family percentages with you during setup.
  • Monitor list (printable): confirmed children with health and allergy information (only if the family gave consent), support needs, image rights and guardian contact.
  • CSV export: every enrollment in the session with statuses and amounts, for the comptroller or the case-management system.
  • Allocation audit: the complete sequence of requests with millisecond timestamps, viewable and exportable as CSV. When a complaint comes in, it shows the real order.
  • Every payment reaches the town’s Redsys TPV: reconciliation uses the municipal bank statement and the order references in the CSV export.
  • The TPV credentials (merchant code, terminal and secret key) are entered on the Redsys settings page. The secret key is stored encrypted and never shown again.
  • If you cancel a paid enrollment, or the bank ever captures a second or late payment, the payment appears in the list of payments to refund. You make refunds from your bank’s TPV administration module: EnaJoin has no refund button and does not move money.