Organization introduction
The Organization module in Drixal ERP holds the operating structure of the business: departments, teams, branches, objectives, holidays, locations, assets and IT systems, plus shared values such as currency, tax rate, and service priority.
Without this module, hierarchy and shared org data stay informal—scattered lists, unclear reporting lines, and lookups that drift between teams. Inside Drixal, Organization keeps structure and reference data tied to the same operating model.
ORG/LineItem has no standalone Organization list page. Commercial line-item UI lives in project and procurement flows. See Project Line Items.
What the module does for your business
- Builds the org tree: Department → Section → Unit
- Manages Teams and their members
- Maintains Branches, Objectives, and Holidays
- Tracks Locations, Assets, and IT Systems
- Holds Organization-side lookups: Currency, Tax Rate, and Service Priority
- Points to shared lookups documented elsewhere: Country, Data Confidentiality, Work shifts
Hierarchy
Organization
├── Department (Section / Unit)
├── Team
│ └── Team Members
├── Branch
├── Objective
├── Holiday
├── Location
├── Asset / IT System
└── Lookups (Currency, Tax Rate, Service Priority)
| Level | Purpose |
|---|---|
| Department | Org tree nodes (department / section / unit), manager, finance links |
| Team | Cross-functional team with lead and members |
| Branch | Branch records with owner and Active flag that persists |
| Objective | Org goals with type, status, and optional owner |
| Holiday | Holiday dates, annual repeat, confidentiality |
| Location | Sites under a branch, with optional parent location |
| Asset / IT System | Trackable items; IT System adds supplier |
| Lookups | Currency, tax rate, service priority used across the platform |
Where to find it in the system
Path: Sidebar ← Organization ← …
From the side menu choose Organization, then (when shown):
- Objective
- Department
- Branch
- Team
Other Organization routes exist by URL even when they do not appear in that nav group (for example Holiday, Location, Asset, IT System, Currency, Tax Rate, Service Priority).
Who uses this section
| Role | Daily use |
|---|---|
| Org / HR administrator | Departments, teams, branches, holidays |
| Operations lead | Locations, assets, IT systems |
| Finance steward | Currency, tax rates |
| Service / SLA steward | Service priorities |
| Project / delivery teams | Objectives and structure used across modules |
How the Organization guide is organized
- Departments — tree, list, structure, employees, record page
- Teams — cards/list, lead, team members
- Branches — list, owner, Active persistence
- Objectives — goals with type and status
- Holidays — dates and annual repeat
- Locations — branch and parent hierarchy
- Assets — serial, values, owner
- IT Systems — asset-like plus supplier
- Currencies — FX and base currency (also see ADM Currencies)
- Tax Rates — percentage, invoice label, default
- Service Priorities — names, descriptions, color
- Glossary
Shared lookups without dedicated Organization docs pages: Country, Data Confidentiality, Work shifts. Line items: Project Line Items.
Best Practices
Create the Department → Section → Unit structure first, then attach teams and people. A team without a clear org context is harder to govern.
On Branch, Active persists. On Location, Asset, and IT System, the Active control is toast-only and does not persist like Branch. Operate accordingly.
Do not expect an Organization Line Item list. Use project line items in PMO (and related module UIs) instead.