Skip to content
    hazBasehazBaseDocs
    API accessGitHub
    GuidesQuickstartMCPSDKHTTP APIPatternsBUILD WITH hazBase
    USE CASES
    ← All use cases

    Community housing operations

    Separate project participation, resident access and operating decisions.

    Equipment & business assetsExample architecture

    The scenario

    ForCommunity housing operators, property businesses and development organizations

    Manage project participants separately from residents of a renovated property. Link agreements, participation units and resident credentials through a property ID.

    What this makes visible

    Connect operating reports and proposals without conflating participation units and residency credentials.

    Token and business-data roles

    Represented by tokens

    Use FlexibleToken for participation units and PrivilegeNFT for individual resident/access credentials. Add GenericGovernor where voting is needed.

    Managed in business systems

    Property ID, participation and tenancy agreements, residency periods, rent, repairs and expenses.

    Map project, asset or order IDs to chainId, contract address and tokenId where applicable. Link the operation ID to the confirmed transaction so the application can trace the result.

    Contract composition

    ContractRole in this use case
    FlexibleTokenManage participation units and holdings.
    PrivilegeNFTIdentify individual access credentials.
    GenericGovernorSupport proposals and votes on operating policies.

    Follow each contract for its key operations, SDK and source. Select the components your workflow needs and connect them to business approvals and records.

    User and processing flow

    1. Define the property and roles

      Define participant, resident and operator rights and responsibilities.

    2. Issue units and credentials

      Issue contract-linked units and resident credentials to their respective holders.

    3. Update operating information

      Link move-ins, departures, repairs and rent records to the property ID.

    4. Report and review

      Share reports and update operating policies through the chosen approval process.

    Operating considerations

    Ending access

    Reconcile application access and token handling when a tenancy or agreement ends.

    Access to records

    Separate resident personal information from operating reports shared with participants.

    Review approvals, reconciliation and recovery

    Implement this use case

    These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.

    Physical assets & inventory

    Connect asset identity and rights to issuance, transfers and holdings.

    Explore the implementation

    Access & membership

    Manage rights to use facilities or services and participation conditions.

    Explore the implementation

    Community & governance

    Design proposals, voting and execution around participants and permissions.

    Explore the implementation
    Start with a sampleDiscuss an integration
    ← Back to all use cases