Company-scoped access
Every customer, user, service, payment configuration, and operational record is assigned to a licensed company boundary.
Security & isolation
Company boundaries are part of the product design.
OrbitWorks separates company configuration, users, operational records, domains, integrations, and payments through explicit access patterns.
Defense in depth
Identity, roles, record scope, credential boundaries, and deployment choice work together.
Role-based administration
Platform owners, company administrators, staff, and customers receive only the capabilities their roles require.
Credential separation
Provider secrets and payment credentials remain in protected server-side boundaries and are never exposed in portal records.
Safe shared tenancy
Shared deployments use enforced company filters, owner-only control-plane access, and explicit integration scoping.
Dedicated deployment option
Companies needing their own OAuth identity, data boundary, or release path can use an isolated deployment.
Auditable workflows
Approvals, status changes, automated jobs, and administrative actions can be recorded for accountability.
Deployment choice
Shared deployment
Efficient, configuration-isolated tenancy.
Companies share the application release while data access, features, branding, processor settings, and tenant context remain company-scoped.
Dedicated deployment
A stronger boundary when requirements demand it.
Use a separate deployment for company-specific OAuth identities, release schedules, data requirements, or custom integration architecture.
Your portal. Your brand. Your operation.