Orchestiva security architecture
Security is the boundary around every action
Every protected request must pass through identity, authority, policy, and tenant-data boundaries before it reaches a business record.
Identity does not replace authorization
Authentication is only the first boundary. Protected operations also require valid tenant and workspace context plus the permission required for the action.
- Validate signed identity and active session claims
- Resolve tenant and workspace context server-side
- Enforce roles and permissions before protected work
Protect credentials and consequential actions
Sensitive provider secrets and automated actions require narrow handling so a convenience feature does not silently expand authority.
- Protect provider credentials outside public records
- Require human review where policy demands it
- Write append-only evidence for important decisions
Questions
What teams usually ask first
Start with the workflow creating the most friction, then expand the workspace deliberately.
How is one business separated from another?
Tenant and workspace context is enforced at the data layer, with forced row-level security and permission-aware server operations around protected records.
Does platform support have permanent tenant access?
No. Support access is explicit, time-bound, scoped, and auditable rather than becoming permanent background access to tenant data.