Skip to main content

Legal and Compliance Configuration

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

ZGRID includes a configuration layer for legal, fee, and building-rule setup. The goal is to keep operational work, billing logic, and building-specific rule application tied to one shared platform model rather than scattering those concerns across spreadsheets or one-off admin actions.

Current Scope​

The current legal and compliance-oriented layer includes:

  • legal foundations
  • jurisdiction profiles
  • fee matrices and related rule inputs
  • building legal settings
  • unit-share readiness and related building-level setup state

Jurisdiction Profiles​

Jurisdiction profiles let the platform carry rule context that applies across more than one organization or building.

Current shape:

  • Back Office holds the platform-level visibility and review surfaces
  • profile and draft-rule work stays on the administrative side of the product
  • manager-facing surfaces consume the resulting configuration through the shared backend model

Legal foundations provide the rule and configuration layer that helps building operations and fee logic stay grounded in a managed structure.

Current shape:

  • the API owns the rule and configuration model
  • managers interact with the resulting settings through Manager Desk
  • platform administrators maintain broader profile and draft lifecycle visibility where required

Building legal settings connect platform-level rule structures to a specific building or organization context.

Current shape:

  • manager organizations can work inside building-scoped legal/configuration surfaces
  • building-level readiness data remains tied to the same tenant and organization model as other operational features
  • legal/configuration state is part of the platform workflow, not an isolated back-office spreadsheet process

Why This Layer Exists​

In ZGRID, legal and fee configuration is not separate from product behavior.

It influences:

  • building readiness
  • fee and share calculations
  • manager-facing operational setup
  • the consistency of downstream billing and reporting flows

Design Principle​

Legal and compliance-related configuration should be:

  • API-owned
  • organization- and building-aware
  • reviewable through controlled admin and manager surfaces
  • documented as product configuration, not as legal advice