Company data isolation
Records are scoped so one client cannot read another company's work or identity.
Security
Client collaboration needs stronger boundaries than a hidden menu.
OrbitOS evaluates access against the signed-in user, their role and their authorized company scope across the application and data layer.
Access architecture
How access is checked
The same authorization principles apply whether work is reached through the interface, a direct URL or a connected AI client.
Role-based permissions
Admins, internal members and external clients receive distinct access and controls.
Internal stays internal
Private notes, rates, costs and margins remain outside the client experience.
Protected direct access
Guessed identifiers and direct links do not bypass authorization checks.
Activity history
Task changes and collaboration events remain available as traceable work history.
Permission-aware actions
Automations and AI task actions follow the permissions of the authenticated user.
Client visibility
What a client user can and cannot do
Client access is deliberately narrower than internal access, with collaboration centered on their own company and visible delivery items.
Client users can
- ✓View their own company dashboard and visible work
- ✓Comment, participate in approvals and create scoped requests
- ✓Access shared documents, goals and progress
- ✓Message the agency team in their own channel
Client users cannot
- ×See other companies or their records
- ×Read internal notes, rates, costs or margins
Built for agency work
Talk through your access model.
Bring your company structure and collaboration requirements to a tailored OrbitOS walkthrough.