Preserve workspace boundaries
A sub-account maintains its own users, reporting relationships, leave records and operational configuration. Account-aware access and database row-level security support tenant isolation.
HourOps for vendor collaboration
Collaborate on projects without merging company workspaces.
HourOps Turbo lets a primary organization create sub-accounts for vendors or affiliated companies. Each account operates in its own tenant context, while shared projects provide the collaboration boundary for task visibility and approved-work invoicing.
Keep vendor users and policies separate
Share selected projects across accounts
Show shared-project tasks with controlled editing
Receive invoices backed by approved timesheets
Inside HourOps
How HourOps supports this workflow
Share intended project context
The primary organization shares a selected project. Employees assigned within that project can see its tasks across participating accounts, while edits remain restricted to authorized ownership.
Approve vendor work before invoicing
Vendor employees record time against assignments. Approved entries become eligible for a sub-account administrator to prepare an invoice request.
Keep the review traceable
The parent organization can approve, reject or request correction. Projects, tasks, hours and commercial details remain connected to the request.
A practical HourOps path
1
Create the sub-account
Give the vendor an isolated workspace.
2
Share selected projects
Expose the required collaboration context.
3
Approve vendor time
Review work before invoice preparation.
4
Review the invoice
Receive a request backed by approved work.