Product features on HaloRT web surfaces, distilled from team releases and VIP Pojokan testing. Full API catalogue: Swagger. Map: Features/Feature Map.
Marketing — Surfaces/Marketing Web
| Feature | URL / notes |
|---|---|
| Company site | https://www.halort.com |
| Community registration | /daftar — slug → {slug}.halort.com, optional custom domain, module preview by community type |
| Contact form | → Notifications |
| Android APK download page | https://www.halort.com/android |
Central shell — Surfaces/Platform Web
| Feature | Notes |
|---|---|
| Login pusat | app.halort.com/login — empty komunitas = platform account; with slug = tenant portal |
| Role picker | If email has both pusat + komunitas roles |
| Platform ops | app.halort.com/platform — approve/reject community applications |
| Magic link + Google | Fixed return_to; see Auth |
Tenant public + resident — e.g. https://gp2.halort.com
| Feature | Notes |
|---|---|
| Public berita / agenda / kampanye / kontak | Unauthenticated browsing |
| Resident portal | After login — iuran, surat, kampanye, pasar, … |
| Iuran | Active once warga identity / unit known |
| Pasar | /pasar, preloved, jualan, jasa, pasang iklan |
Admin komunitas — /admin
Aligned with Concepts/Roles and Portals (admin / pengurus):
- Dashboard, warga, iuran, berita / pengumuman
- Pengaturan → Modul Fitur (enable/disable modules)
- Publish pengumuman (feeds mobile push test scenarios)
- Backend-backed: user delete with hierarchy checks, galeri albums, public pengeluaran/donasi, Excel exports (kependudukan, arus kas, iuran, pengeluaran) — Surfaces/Platform API
Notifications tied to web actions
Email / WhatsApp hooks for donation & iuran verify/reject, optional announcement fan-out — Notifications.
How we test web
See Testing/Web Admin Checklist · Testing/Testing Mechanism · cross-check with Testing/iOS TestFlight Checklist / Testing/Android APK Checklist.
Related
Surfaces/Platform Web · Surfaces/Marketing Web · Features/Mobile Features · Tenant · Architecture/Request Flow