Security & Tenant Isolation

Customers never touch the owner’s mega brain.

The SaaS layer is separated from the owner/admin layer. Customer commands are scoped to the customer workspace. Owner production credentials, admin ledgers, social connectors, and orchestrator power stay behind admin controls.

Owner-only credentials

Social, email, production, deployment, and automation credentials should live server-side inside Worker secrets and admin-only configuration.

Customer-scoped commands

Customers can request tasks, build their company profile, select services, and manage their workspace without changing the master platform.

0meg4kAI review

0meg4kAI checks for privilege escalation, connector misuse, unsafe claims, cross-tenant access, and approval requirements.

The rule: customers can run their workspace, not your company.

That is the entire point of the security model. The system is built for autonomy, but autonomy must be permissioned, auditable, and tenant-scoped.