Skip to main content

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.

Line items are documented in PMO

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)
LevelPurpose
DepartmentOrg tree nodes (department / section / unit), manager, finance links
TeamCross-functional team with lead and members
BranchBranch records with owner and Active flag that persists
ObjectiveOrg goals with type, status, and optional owner
HolidayHoliday dates, annual repeat, confidentiality
LocationSites under a branch, with optional parent location
Asset / IT SystemTrackable items; IT System adds supplier
LookupsCurrency, 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​

RoleDaily use
Org / HR administratorDepartments, teams, branches, holidays
Operations leadLocations, assets, IT systems
Finance stewardCurrency, tax rates
Service / SLA stewardService priorities
Project / delivery teamsObjectives and structure used across modules

How the Organization guide is organized​

  1. Departments — tree, list, structure, employees, record page
  2. Teams — cards/list, lead, team members
  3. Branches — list, owner, Active persistence
  4. Objectives — goals with type and status
  5. Holidays — dates and annual repeat
  6. Locations — branch and parent hierarchy
  7. Assets — serial, values, owner
  8. IT Systems — asset-like plus supplier
  9. Currencies — FX and base currency (also see ADM Currencies)
  10. Tax Rates — percentage, invoice label, default
  11. Service Priorities — names, descriptions, color
  12. Glossary

Shared lookups without dedicated Organization docs pages: Country, Data Confidentiality, Work shifts. Line items: Project Line Items.

Best Practices​

Build the department tree before teams

Create the Department → Section → Unit structure first, then attach teams and people. A team without a clear org context is harder to govern.

Know which Active switches persist

On Branch, Active persists. On Location, Asset, and IT System, the Active control is toast-only and does not persist like Branch. Operate accordingly.

No LineItem page under Organization

Do not expect an Organization Line Item list. Use project line items in PMO (and related module UIs) instead.