Mortezakoohjani 12c8615615 Ship enterprise Accounting FE/API with CRUD parity and production wiring.

Adds accounting-service PATCH/archive, fiscal helpers, COA templates and setup status, plus SuperApp Accounting UI (DS, scoreboard, masters, vouchers, ledger, ops modules) with session refresh and HTTPS public API URLs.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-07-24 15:26:43 +03:30

1.2 KiB

Raw Blame History

ADR-003: Row-Level Multi-Tenancy with tenant_id

Field	Value
Status	Accepted
Date	2025-01-01
Deciders	Platform Architecture
Supersedes	—
Superseded by	—

Context

Every business module must isolate tenant data. Database-per-tenant is operationally heavy for early phases.

Decision

Use shared databases per service with mandatory tenant_id on every business table. Tenant resolution order: X-Tenant-ID → X-Tenant-Slug → subdomain → custom domain → user current_tenant_id. Cross-tenant queries are forbidden.

Consequences

Positive

Simple ops on a single DB per service
Consistent middleware and repository filters
Compatible with subdomain and custom-domain white-label

Negative

Requires rigorous tenant filters in every query
Noise-neighbor risk at very large scale (future mitigation possible)

Alternatives Considered

Database-per-tenant
Schema-per-tenant

1.2 KiB Raw Blame History