Bank file import
Import bank statements (camt.053, camt.054, MT940 or CSV). Payments are matched to invoices and marked paid, other bookings go into the books by your rules, with a dry run first.
Import bank statements (camt.053, camt.054, MT940 or CSV). Payments are matched to invoices and marked paid, other bookings go into the books by your rules, with a dry run first.
A yearly budget per transaction category, compared with what was booked. Approve and lock it, and copy it to the next year.
The Hubra bot on your Discord server: announcements, roles, group channels, Discord events, poll buttons, personal commands and direct messages.
A usage guide per machine or tool, in Markdown or as a link to a manual or video, shown on the inventory item.
Physical keys, cards and fobs: who holds which, with a handover log. Members see their keys on their account page.
Read club mailboxes hosted anywhere (Infomaniak, Hostpoint, Gmail with an app password...) inside Hubra. Read-only by default, each mailbox visible to one group, passwords stored encrypted.
This list comes from index.json, signed with the Hubra index key.
A plugin runs with access to the platform's data. So only Hubra's platform admins install plugins, after a review, in the plugin catalogue.
Under Settings › Modules & plugins you switch a plugin on or off for your club, like any built-in module.
Every version is signed and comes with its changes. A Hubra installs only what is signed with a key it trusts, and can go back to the previous version.
From the template to a signed release: layout, backend, frontend, tests and publishing.
Build a plugin → SecurityPlugins and the index have separate keys. Every Hubra checks both when it installs, and every plugin's source code is public.
Security at Hubra →