Skip to main content

Features by Application

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

This page is the practical feature map by application. It is meant to answer: “What exists today, what is partial, and what is only scaffolded or placeholder-ready?”

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

Implemented:

  • auth, session refresh, logout, and current-context flows
  • role and scope enforcement for tenant, manager, technician, and super_admin
  • tenant onboarding and technician onboarding route groups
  • building hierarchy and building-context APIs
  • issues workflow including comments, attachments, work logs, and feedback
  • service requests, conduct reports, help requests, resident directory, documents, announcements, voting, reserve funds, debtors, and notifications
  • 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/storage integrations through environment-managed configuration

Partial:

  • some newer cross-cutting integrations such as email foundation and monitoring are still settling into broader operational documentation
  • 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

Implemented:

  • sign-in and guarded admin shell
  • overview dashboard
  • organizations and subscriptions views
  • organization-level feature entitlement controls
  • issue list/detail for platform-level visibility
  • privacy deletion request processing
  • audit log and admin profile surfaces
  • system health screens backed by optional uptime integration

Partial:

  • deployment automation is not described as fully as Manager Desk and API in the current repo workflow docs

Template-ready:

  • a fully documented Back Office deployment playbook is not yet captured in the docs portal

Related docs:

Manager Desk​

apps/manager-desk

Implemented:

  • sign-in, workspace shell, and dashboard
  • buildings and unit structure management
  • issues operations and service request manager flows
  • tenant onboarding request review
  • representatives management
  • announcements, documents, votes, invoices, reserve funds, debtors, maintenance, notifications, profile, and settings surfaces
  • subscription page for plan, usage, access mode, and billing controls

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

Implemented:

  • tenant login, session restore, logout, and profile/legal/privacy surfaces
  • tenant issue reporting and issue detail/list screens
  • announcements, documents, voting, reserve funds, notifications, resident directory, and service request 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 is feature-gated and may intentionally resolve to a limited fallback path
  • 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 internal documentation
  • categorized sidebar for onboarding, applications, environments, architecture, operations, QA, product, external services, and reference
  • docs build validation through corepack pnpm run docs:build

Partial:

  • content depth varies by topic area
  • some operations pages remain intentionally placeholder-oriented where the repo does not yet define a stronger standard

Template-ready:

  • public hosting and permanent internal dashboard links are not yet standardized in repo docs

Related docs: