Skip to content
Qtangl logo mark
Qtangl

Developer portal

Data model guide

Qtangl data model prioritizes strict tenant isolation, complete auditability, and controlled deletion workflows.

Last updated: 2026-06-09

Multi-tenancy and isolation

Tenant-scoped APIs enforce access boundaries at auth and data layers. Tenant metadata can be retrieved using GET /tenant/me, while admin control plane actions remain on /admin/* endpoints.

RLS-aware data access patterns

  • Use tenant routes such as GET /tenant/scans and GET /tenant/audit for scoped reads.
  • Export tenant-bounded data with GET /tenant/export.
  • Keep cross-tenant workflows in explicit portfolio endpoints only.

DSAR and offboarding lifecycle

DSAR and tenant decommission workflows should run through DELETE /tenant/data and POST /tenant/offboard. Capture immutable audit exports before destructive steps to meet legal hold and compliance obligations.

Governance controls

Found an issue? Report documentation feedback