Skip to main content

Features by Application

Last reviewed: 2026-06-13
Maintained by: Engineering

This page is the practical feature map for ZGRID. It answers a simple question: what is live today, what is still partial, and what exists as structure without a fully standardized rollout.

Status legend:

  • Implemented: backed by current code paths and current repo docs
  • Partial: present, but gated, incomplete, or not fully automated/documented
  • Template-ready: documentation or structure placeholder exists, but a full standard or deploy path is not yet defined

For a lower-level repository inventory, also see Features Inventory.

API Backend​

apps/api

The API is the shared operating core behind every ZGRID surface.

Implemented:

  • auth, account, session refresh/logout, and current-context flows
  • role and scope enforcement for tenant, manager, technician, and super_admin
  • tenant onboarding, technician onboarding, and manager/representative onboarding route groups
  • building hierarchy and building-context APIs
  • issues workflow including comments, attachments, work logs, reopen/review state, and feedback
  • announcements, documents, building decisions, resident directory, notifications, and device-installation/push support
  • service requests, help requests, conduct reports, and noise notices
  • billing, invoices, ledger/reconciliation, reserve funds, debtors, and resident payment attempt flows
  • legal foundations, jurisdiction profiles, building legal settings, and fee/share support
  • reports and export surfaces for manager-facing operational data
  • admin platform endpoints for organizations, subscriptions, feature entitlements, issues, privacy queue, and audit
  • environment validation, migration commands, seed flows, and schema drift checks
  • optional monitoring, email, and storage integrations through environment-managed configuration

Partial:

  • some cross-cutting integrations still depend on hosted configuration or operational follow-through
  • no always-on in-process scheduler is documented; cleanup/retention behavior remains workflow/script-driven

Template-ready:

  • alternate API hosting patterns outside the current Render setup are not standardized in repo operations docs

Related docs:

Back Office​

apps/back-office

Back Office is the platform control layer for super_admin users.

Implemented:

  • sign-in and guarded admin shell
  • overview dashboard
  • client directory, organization detail, and subscription views
  • organization-level feature entitlement controls
  • resident payment configuration controls
  • issue list/detail for platform-level visibility
  • jurisdiction profiles, fee matrix, coefficients, and rule-draft review surfaces
  • privacy deletion request processing
  • audit log and admin profile surfaces
  • system health screens backed by optional uptime integration
  • desktop and larger-tablet workflow with MobileGuard for viewport widths below 960px

Partial:

  • some operational/hosting detail is intentionally omitted from the public docs view

Template-ready:

  • some deeper administrative operating guidance remains intentionally internal

Related docs:

Landing​

apps/landing

Landing presents the ZGRID product story and captures early commercial interest.

Implemented:

  • public marketing site
  • locale-aware public routes with / redirecting to /bs
  • Bosnian page at /bs
  • English page at /en
  • server-backed contact flow for landing inquiries

Partial:

  • hosted domain rollout can remain on preview/staging subdomains before promoting the final public domain setup

Template-ready:

  • private preview/noindex handling depends on the final Vercel preview policy

Related docs:

Manager Desk​

apps/manager-desk

Manager Desk is where building operations, communication, legal settings, and financial visibility come together for manager organizations.

Implemented:

  • sign-in, workspace shell, and dashboard
  • buildings and unit structure management
  • issues operations, service request manager flows, and technician coordination surfaces
  • tenant onboarding plus manager/representative onboarding review flows
  • representatives management
  • announcements, documents, building decisions, invoices, reserve funds, debtors, maintenance, notifications, profile, and settings surfaces
  • legal foundations and building legal settings surfaces
  • building reports/export-oriented screens
  • subscription page for plan, usage, access mode, and billing controls
  • desktop and larger-tablet workflow with MobileGuard for viewport widths below 960px

Partial:

  • feature availability still depends on current entitlements and organization state
  • some feature modules may continue to evolve alongside backend entitlement rules

Template-ready:

  • no separate manager-only public documentation site or hosted handbook is defined outside this portal

Related docs:

Mobile App​

apps/zgrid-mobile

Mobile keeps residents and technicians connected to the operational flow without asking them to work inside the internal web tools.

Implemented:

  • tenant login, session restore, logout, and profile/legal/privacy surfaces
  • tenant issue reporting and issue detail/list screens
  • announcements, documents, building decisions, reserve funds, notifications, resident directory, and service request flows
  • help requests and noise notice flows
  • onboarding pending/rejected states
  • technician jobs, issue detail, setup, and profile routes
  • Expo push registration flow in the mobile/client/API integration

Partial:

  • resident payments are feature-gated and may intentionally resolve to a limited fallback path
  • current payment-provider implementation remains mock/staging-provider oriented; do not treat production resident card payments as live
  • representative-specific user experience remains narrower than the backend/context support

Template-ready:

  • operational mobile dashboard/link documentation is currently placeholder-based in this portal

Related docs:

Docs Portal​

apps/docs plus repo-level docs/

Implemented:

  • Docusaurus portal for public-safe technical documentation
  • categorized sidebar for applications, environments, architecture, product, and stable reference material
  • docs build validation through corepack pnpm run docs:build

Partial:

  • content depth varies by topic area
  • some internal-only operating material is intentionally not part of the public docs build

Template-ready:

  • documentation depth can still expand without exposing internal dashboards or private operations detail

Related docs: