Platform
Hybrid Roles (Developer / Subcontractor)
The same company can be the developer on one project and a subcontractor on another; the menu adapts to the selected project.
What is it for?
BuildOS does not label companies as "developer only" or "subcontractor only". Every registered company is an organisation; the same company can be the developer on its own land and a contracted subcontractor on another company's project. There are no separate panels: your own projects and the projects you joined as a subcontractor sit together in the project list, and the menu adapts to your role in the selected project. On your own project you use all of BuildOS; on someone else's project you see what the developer allows plus your own work (warehouse, attendance, diary, your subcontractors).
How does it work?
- 1A company is created at sign-up; a user can belong to one or several companies.
- 2The project picker lists your own projects together with the projects you joined ('Subcontractor · developer name').
- 3On your own project you create projects, tenders and contracts; on a project where you are a subcontractor you see your contract, work entries, payments and your own subcontractors.
- 4When you switch project, the menu and screens adapt to your role in it; no panel switching is needed.
Highlights
- The role comes from the project, not fixed to the company.
- Membership in several companies and one-click company switching.
- All modules on your own project; on others' projects, as much as the developer grants and your trade allows.
- A subcontractor can build its own contract and payment chain with lower subcontractors; the developer sees it all.
As a developer (employer)
Uses all modules on its own projects and sets participants' access.
As a subcontractor
Runs its own work on the joined project and, if needed, manages its own subcontractors.
How it connects to other modules
Roles control the visibility of all modules through Contracts (which link both parties), Projects, Permissions and the project picker.