Skip to content
ZekaForge
Platform

Organizations, roles & tenant isolation

How ZekaForge keeps each organization’s data separate, and what each role can do.

ZekaForge is multi-tenant: many organizations share the platform while their data stays strictly separated.

How isolation works

Every tenant-owned record carries an organization_id. A global query scope automatically constrains every read to the active organization, and new records are stamped with it automatically. A dedicated test suite asserts that one organization can never read another's rows.

Roles

Role Typical use
Owner Full control, billing, delete organization
Administrator Manage members, settings, API keys
Developer Device sessions, tests, applications
Security Analyst Scans, findings, reports
Viewer Read-only access

Switching context

A user can belong to multiple organizations. The "current organization" determines which workspace they are acting in; middleware verifies membership before activating that tenant.

Why shared-schema

For the MVP, shared tables with an organization_id keep cost and operations simple. For large enterprise customers, the architecture can evolve toward schema- or cluster-per-tenant without changing the application's tenant API.

Partager

Articles liés

Commencez avec ZekaForge

Créez un compte gratuit et explorez Device Cloud et Cyber AI en quelques minutes.