Master data
Organizations
The organisation tree — departments, regions, suppliers and the hierarchy that drives workflows, who sees what, and how you report.
Updated Jan 23, 2026
Configuration · Masterdata · 4M.2
Organizations are the backbone of Gfacility — not just a list of departments, but the hierarchy that drives how workflows run, who has access to which data, and how you report. Whether you’re dealing with internal teams, external suppliers or regional divisions: this is where you set out who belongs to whom.
Why this matters to the business
"Numbers per department impossible"
Tree depth = reporting depth. The level you record at is the level you can analyse at.
"Approver differs per department"
Members on an organization → approval routes are derived automatically.
"International chargeback"
Time zone and currency per organization → figures, planning and invoices follow the right context.
"Suppliers see each other's work"
Master filters on organization → external parties see only their own scope.
Three functions of the organisation tree
Reporting
Down to which level do you want figures? Company, department or sub-team? Tree depth is reporting depth.
Routing
Workgroups can be derived automatically from organization. Tickets and tasks reach the right people directly.
Segregation
The tree feeds filters and security. Users see only data from their own entity, or across the board.
What do you set per organisation?
| Field | What it does |
|---|---|
| Name, code & description | Identification. Code is handy for exports and integrations. |
| Type | Internal, supplier, customer, region — comes from classifications. Drives filters and rules. |
| Time zone & currency | For international entities — calendars and financial figures in the right context. |
| Parent | Higher-level organisation. Determines where this entity sits in the tree. |
| Finance | Cost centre, budget categories — defined in the financial settings. |
| Members | People or workgroups with a role — source for approvers and notifications. |
Which decisions will you make?
At which level do you report?
Company level, department, sub-team — drives tree depth. Too deep = admin overhead, too shallow = blind to detail.
Do you work with regions?
Want to report on "Region South"? Then that region has to be an organisation entity.
Which organisation types do you distinguish?
Internal, supplier, customer, region — affects filters, dashboards and which rules apply.
Approvers via members?
Auto-route approvals through organisation members, or rather through separate workgroups?