Business Units in PSOhub
Understand how business units structure your organization and how they impact projects, users, and reporting
Updated: 1 April 2026
Audience
- PSOhub Admininstrator
Objective
Understand how business units organize your company structure in PSOhub and how they influence project ownership, resource allocation, and reporting.
Overview of Business Units
Business units define the organizational structure within PSOhub. They represent how your company is divided, such as departments, teams, or legal entities.
Business units act as the structural layer that connects users, projects, and financial data across the system. They ensure that work, resources, and reporting are aligned with your internal organization.
Key Components of Business Units
Users
Users are assigned to a business unit. This defines their primary organizational context and determines how they are grouped for planning and reporting.
Team Leads
A team lead can be assigned to a business unit. This supports ownership and can be used in approval workflows and management structures.
Integrations
Each business unit can be connected to external systems, such as accounting integrations. This allows financial data to be managed per organizational entity.
How Business Units Fit into the Workflow
Business units are applied early in the system setup and flow through all operational and financial processes.
Typical workflow:
Organization Setup → Business Units Defined → Users Assigned → Projects Created → Business Unit Assigned → Time Entries & Invoices Inherit → Reporting & Filtering
- Projects are assigned to a business unit at creation
- Time entries follow the project’s business unit
- Invoices inherit the same structure
- Reports use business units for segmentation
This ensures consistency across planning, execution, and financial tracking.
Relationships Between Business Units and Other Objects
Projects
Each project belongs to a single business unit. This determines ownership, structure, and reporting.
Users
Users are assigned to a primary business unit but can work across multiple business units through project assignments.
Cross-Business Unit Collaboration
Business units define structure, not restrictions. Resources can be shared across business units when needed.
Hierarchy and Structure
Business units can be structured hierarchically using parent-child relationships.
This enables:
- Department-level structuring
- Regional segmentation
- Multi-entity organizations
There is no limit to hierarchy levels, allowing flexible scaling.
Default System Behavior
When PSOhub is first set up:
- A default business unit is created
- All users are assigned to it
- All projects inherit it by default
📌 Note: This ensures a consistent starting point. Additional business units can be added later without disrupting existing data.
Reporting and Filtering
Business units enable segmentation across the platform.
They are used in:
- Reports
- Financial analysis
- OData and exports
This allows performance tracking across departments or entities.
When to Use Business Units
Use business units when your organization requires structured separation of work or reporting.
Examples:
- Multiple departments (Consulting, Support, Sales)
- Multiple legal entities
- Regional teams
- Financial segmentation
Common Misconceptions
Users can only work within their business unit
Users can be assigned to projects across different business units.
Business units are only for reporting
They also impact project ownership, planning, and financial flows.
Next Steps
Follow this article to start using business units effectively: