Members and onboarding
A member directory with roles and optional contact details, plus a welcome checklist for newcomers.
Implemented
← Back to all projects
Applications
Verger Associations
One app to run an association: organise work, make collective decisions, coordinate volunteers and talk in an encrypted private group.
An Android alpha build passed automated tests on 7 November 2026. A limited pilot is under way, but real-device checks and cross-device association data synchronization are still needed before a public release.
What is Verger Associations for?
Meetings, collective decisions, assigned tasks, welcoming members, running events and requesting help are often scattered across different tools. Verger Associations brings these activities together for associations, community groups and cooperatives.
On launch, users choose the access journey that fits their role. Once signed in, they reach their association dashboard. The end-to-end encrypted SimpleX messaging engine is built into the APK: no separate chat app needs installing.
Features already developed
These features exist in working prototypes or development branches. Code availability does not yet mean production deployment has been approved.
Meetings and decisions
Agendas, proposals, objections, amendments, decision methods, meeting records and follow-up actions.
ImplementedTasks and responsibilities
Assigned tasks, due dates, progress and links back to meetings.
ImplementedEvents and volunteering
Events, attendance tracking, volunteer requests and assignments.
ImplementedMutual aid, ideas and resources
Requests and offers of help, an ideas board, notes and useful links.
Working prototypeVerified consultations
Authenticated accounts, server-side roles, one revisable choice per member, closure and aggregate results. Authorization checks run on the server.
Pilot API and automated testsEncrypted group messaging
SimpleX built into Android: authenticated presidents can create the private group, members join by invitation, and Android Back returns to the signed-in dashboard.
Compiled alpha APK · device retest pendingAssociation setup
Setup wizard, logo, association colour and modules, administrator account, followed by DNS TXT or HTTPS file verification of domain control.
Implemented in pilotAdministration and access requests
Dedicated login, review of volunteer and board requests, and invitation-code generation. The opening-screen role button does not grant privileges.
API and interface automatically testedOffline use and backups
Local Automerge data, portable JSON backup/import, Markdown reports and ICS exports. Cross-device document synchronization is not enabled yet.
Local storage works · sync unavailableAdaptive association colours
One association colour generates harmonious variations for backgrounds, cards, buttons and chat bubbles in light and dark modes, with contrast adjustments.
Included in the latest APKThree access paths for association members
The opening screen shows these paths in the order below. Choosing a button does not grant permissions: actual privileges come from the account verified by the server.
Volunteers
Sign in, request access to the association, or accept an invitation. Once approved, use the modules made available to members.
Board / founders
Sign in to the association, request a suitable level of access, or use an invitation code. This choice does not automatically confer administrator privileges.
Presidency / co-presidency
Create and verify the association space, or sign in with an existing administrator account. Administrators can review access requests and set up encrypted group chat.
Administrators review access requests and, when approved, generate an invitation code to share manually. Automatic email delivery and email-address ownership verification are not yet available.
How does an association set itself up?
- Choose “Presidency / co-presidency”. Create an association space or sign in with an administrator account.
- Introduce the association. Enter its name and description.
- Personalise the interface. Add a logo, pick one accent colour that is automatically applied throughout the interface, and select the modules you need.
- Set up an administrator. Supply an email address and create the administrator account.
- Verify the domain. Either add a temporary DNS TXT record or download a verification text file to place in your website’s public root; the server checks your chosen method.
- Start using Verger. Open your chosen tools from the dashboard; sensitive settings are kept in a separate administrator area.
DNS TXT or HTTPS file verification shows that the person technically controls the domain or website, not that they have proven their legal mandate to represent the association. No hosting password or domain registrar credentials are required.
Public registration is not available yet: this is a restricted pilot. DNS TXT or HTTPS file verification establishes technical control of a domain, not legal authority to represent an association. Expired verification challenges must be generated again. On Android 10+, the proof file is saved directly to Downloads.
Embedded encrypted messaging, not a social network
In the current Android alpha, an authenticated president can open the private-group creation form directly, without supplying a group invitation code. Other members join via an invitation. A first-time encrypted messaging profile is still required, but SimpleX does not need to be installed separately. End-to-end encryption is powered by SimpleX Chat.
The selected group is linked locally to the association on that phone. The latest APK preserves the signed-in Verger dashboard behind messaging so Android Back can return to it. Automated tests passed, but the actual group-creation and navigation flows still need checking on a phone. Group-level permissions remain under SimpleX, and some native chat screens may still include English text.
A shorter mobile navigation
After signing in, four primary destinations appear on smaller screens:
HomeEventsMessagingMore
“More” contains the other enabled modules. A separate sign-in area is used for administration, keeping technical settings apart from the everyday member tools.
What is tested, and what is still missing?
Implemented and automatically tested
PWA association features, exports, identified consultations, access requests, server-side roles, DNS TXT/HTTPS file verification, and adaptive colour palettes are covered by automated tests. The pilot server is running over HTTPS and handles accounts.
Integrated in the Android prototype
The same APK embeds Verger and the SimpleX messaging engine. President-led group creation, navigation back to the signed-in home screen, and association theming are included in the successful 7 November 2026 build. Full device testing remains necessary.
Required before wider availability
Actual association-data synchronization across members and devices, complete permissions for local data, Android testing across devices and versions, end-to-end invitation/revocation testing, remaining translations, and security review before public availability.
Two separate systems: SimpleX messages use end-to-end encryption, but association management data is not automatically encrypted. The pilot server already handles accounts, invitations and consultations, while Automerge document synchronization between phones is not yet enabled. Data stays local to each device and can be lost after uninstalling without a backup.
Verger does not yet replace association accounting, formal records management or production handling of sensitive information.
Source code and participation
Work continues in two repositories: association tools, tests and the pilot server, and Android encrypted messaging integration. The setup guide documents the procedure and current limitations.
7 November Android alpha APK (GitHub Actions) Association tools source code Android messaging source code
The APK is inside the “verger-simplex-prototype” artifact on the GitHub Actions page (GitHub sign-in may be required). It is a test build, not a production release. Back up local data before replacing or uninstalling an earlier version.
Verified on 7 November 2026 against both project repositories, the Android build and the pilot server. Alpha testing only; no stable public release announced.
← Back to all projects