Organization - Human Resources

Overview

Organization lives in the Human Resources sidebar group, right after Org Chart. It is the single place where your company's structural building blocks — Departments, Titles, and Branches — are created and maintained as real records with their own IDs, rather than typed as free text on each employee's profile.

Historically, an Employee record stored "Department" and "Title" as plain text fields: whoever created the employee typed "Engineering" or typed "Engineerng" by mistake, and the platform had no way to know these were meant to be the same department. Organization fixes this by giving Departments, Titles, and Branches first-class records that the rest of the platform — CRM, Project Management, Asset Manager, and Employee profiles themselves — can reference by ID going forward.

What "Master Data" Means Here

A master-data record is a single, authoritative definition of something that many other records need to point to. Before Organization existed, "department" was just a text string copied into every Employee row — easy to misspell, impossible to rename in bulk, and meaningless as a filter key across modules. Now a Department is a record with an ID, a name, a parent (for hierarchy), a manager, and a description. Employees, and eventually CRM territories, Project Management teams, and Asset Manager assignments, will reference that ID instead of retyping the name — so renaming "Engineering" to "Product Engineering" updates every place that references it, instantly and consistently.

Three Tab Groups

Organization groups its tabs into three logical sections, selectable from the pill switcher above the tab bar: Organization (structural master data), Document Library (company-wide files), and Policies & Rules (HR policy master data).

Organization Group — Five Tabs

The first group has five sections. Four are CRUD (create, edit, delete) master-data tables; the last reuses the existing Org Chart visualization.

Departments

Manage the company's department hierarchy. Each department has a Name, a Domain (the add-on module it belongs to, or Global for company-wide), an optional Parent Department (so departments can nest — e.g. "Frontend" under "Engineering"), a Manager, and a Description. Because a department can point to another department as its parent, you can model as deep an org structure as your company needs.

Titles

Manage job titles as their own records: Name, a numeric Level for seniority ranking (e.g. junior/mid/senior), a Department reference linking the title to the department it typically belongs to, and a Description. Titles are no longer free text on an employee — they're picked from this list.

Branches

Manage physical office and site locations: Name, City, Phone, Manager, and Address. Useful for any company with more than one physical location — headquarters, regional offices, warehouses — that needs to track which employees or assets belong to which site.

Roles & Permissions

The master view of every role across every add-on domain in one table. HR can create new roles, edit any role's capabilities, and delete them — with a role's Domain, Category, and Type (Default vs. Custom) shown as sortable columns. Roles created here flow straight to the matching add-on's own Roles screen, and vice versa.

Org Chart

Embeds the existing Org Chart visualization showing the reporting hierarchy of employees — who reports to whom, drawn as a tree. This tab doesn't duplicate the Org Chart's own logic; it's the same component reused here for convenience, so you can move between structural master data and the visual reporting chart without leaving the screen.

Pagination

Every table tab in Organization shows up to 15 rows per page with page controls at the bottom; the Org Chart tab is exempt. Search, filters, and column sorting all apply before pagination.

Managing Departments

Open the Departments tab.
Click Add Department to open the add/edit modal.
Enter a Name (required).
Pick a Domain (required) — the add-on module this department belongs to (e.g. Healthcare, Legal, Construction), or Global — All Domains for a company-wide department. The Domain shows as a colored badge in the table.
Optionally pick a Parent Department — leave empty for a top-level department, or choose an existing department to nest this one underneath it.
Optionally pick a Manager from a dropdown of your Employees, and add a free-text Description.
Click Save. The department appears in the table immediately, and becomes selectable as a Parent Department for future departments, as the Department reference on Titles, and as a choice on the Employees screen's Add Employee form.

To edit or remove a department, use the row's Edit or Delete action; deleting shows an inline confirmation before the record is removed.

Departments Sync Two Ways with Add-On Screens

Organization is the single source of truth for departments, but each add-on that has its own Departments screen (e.g. Healthcare → Departments & Wards) reads and writes the same store. A department you create in Healthcare with domain Healthcare appears here automatically; a Healthcare department you create here appears on the Healthcare screen. An add-on screen shows only its own domain's departments (Global departments stay in HR Organization only) — so the Healthcare screen never lists a Legal or Global department.

Add-on–specific detail lives with the add-on: Healthcare, for example, keeps a department's Type (Polyclinic, Inpatient Ward, ICU, Operating Room, Emergency, Laboratory), head doctor, charge nurse, rooms and beds on its own screen. HR Organization shows that Type as a read-only column — filled in for Healthcare departments and shown as "—" for every other domain.

Managing Roles & Permissions

The Roles & Permissions tab is the master matrix of every role across every add-on domain — HR sees them all in one place, can filter by domain, and can create, edit, or delete any role. Roles are the same records the add-ons' own Roles screens use, so changes flow both ways instantly.

Open the Roles & Permissions tab.
Click Add Role to open the create modal.
Enter a Role Name. A Role Code is auto-generated from the name (e.g. "Senior Site Inspector" → SENIOR_SITE_INSPECTOR); you can override it, after which it stops auto-filling.
Add an optional Description.
Pick a Domain (required) — the add-on the role belongs to, or Global — All Domains. A Global role appears on every domain's Roles screen; an add-on role appears only on that add-on's screen (and here).
Pick a Category, filtered to the selected domain's categories. Use + Add New to create a category inline without leaving the modal.
Select Capabilities, shown in two labeled groups: Physical / Operational Capabilities (the cross-cutting Global capabilities — Technician, Driver, Picker, Operator) and Domain-Specific Capabilities (the selected domain's own permissions).
Click Save. The role appears here and on the matching add-on's Roles screen with no extra steps.

The table lists each role with its Domain, Category, and Type (Default = shipped template, Custom = created by you). Click the Domain, Category, or Type column header to sort by it; click again to reverse the direction. Use Edit to adjust a role's capabilities or Delete to remove it (with inline confirmation).

Where Roles Come From

Every add-on ships with default roles and can define its own on its Roles screen. This master tab is where HR governs all of them together — no matter which screen a role was created on, it lands in the same per-tenant store and stays in sync everywhere it's shown.

Managing Titles

Open the Titles tab.
Click Add Title.
Enter a Name (e.g. "Senior Software Engineer").
Set a numeric Level to indicate relative seniority — useful later for sorting, filtering, and reporting on career progression.
Optionally link the title to a Department from the list you maintain in the Departments tab.
Optionally add a Description.
Click Save.

Managing Branches

Open the Branches tab.
Click Add Branch.
Enter a Name (e.g. "Istanbul HQ").
Fill in City, Phone, and Address as applicable, and optionally pick a Manager from a dropdown of your Employees.
Click Save. The branch becomes selectable on the Employees screen's Add Employee form.

The default sample tenant ships with three branches out of the box — Istanbul HQ, Ankara Office, and Izmir Warehouse — as a starting reference for how a multi-location company might set this tab up.

Viewing the Org Chart

The Org Chart tab shows the same reporting-hierarchy visualization available elsewhere in Human Resources — it is not a separate copy, but the same component embedded here for convenience. Use it to check reporting lines while you're already working on department and title structure, without switching screens.

Document Library

Switch to the Document Library group to reach the Documents tab — a company-wide file library for internal regulations, leave request forms, offer letter templates, and similar shared documents. This is distinct from the per-employee document records in Document Entry: files uploaded here belong to the company, not to any individual employee.

Pick a category from the dropdown — Regulation, Leave Form, Template, Offer Letter, or Other.
Click Upload Document and choose a file. The file name (without its extension) becomes the document's title automatically.
The uploaded file appears in the table with its category and upload date. Use the download icon to open it, or delete it with inline confirmation.

Policies & Rules

The Policies & Rules group holds the HR policy master data that other HR screens read from — three tabs:

Leave Rules

One rule per leave type (Annual, Sick, Personal, Bereavement, Paternity, Maternity): annual entitlement in days, how many days can carry over into the next year, and whether the leave type requires manager approval. This is the policy behind the numbers — separate from individual leave requests, which are tracked elsewhere in Leave Management.

Work Calendar & Holidays

The company's official holiday calendar: each entry has a Name, a Date, and whether it Recurs every year (e.g. national holidays) or is a one-off (e.g. a specific year's religious holiday date). The default sample tenant ships with the standard Turkish national holidays as a starting reference.

Asset Types

The controlled list of equipment categories HR is allowed to hand out — Laptop, Phone, Tablet, Monitor, Access Card, Meal Card, Company Car, and any custom types you add. This is policy-level: it defines what categories exist, before any individual physical unit is registered in Asset Manager.

AI Assistant

Organization includes a built-in AI Assistant, opened from the collapsed AI Assistant tab anchored to the right edge of the screen (click it to slide the panel open; click the tab on the panel's own left edge, or its header X, to close it again). It answers questions grounded in all of the screen's master data at once — Departments, Titles, Branches, Leave Rules, the Work Calendar/Holidays list, Asset Types, and the Document Library's file count — regardless of which tab or group is currently active. Example questions it can answer:

A summary of the department hierarchy, or which departments have no manager assigned
Coverage gaps — titles with no department reference, or departments with no titles
Policy questions — leave entitlements, upcoming holidays, or what an asset type is meant to cover
Consistency checks — things that look off, like a very high seniority level with no clear department

Why This Matters for the Rest of the Platform

Departments, Titles, and Branches created here are designed to be referenced by ID from other modules over time:

Module	How it will use Organization records
Employee profiles	Department and Title fields point to real records instead of storing typed text, so renames and reorganizations propagate automatically.
CRM	Sales territories and account ownership can reference Branches and Departments for accurate regional reporting.
Project Management	Teams and resource assignments can filter and group by Department instead of free-text labels.
Asset Manager	Equipment assignment and reporting can be grouped by Branch — e.g. "all laptops assigned to the Izmir Warehouse."

This migration happens gradually, module by module — existing free-text data is not silently rewritten. Organization's job is to give every module a consistent, ID-based place to point to as each one adopts it.

Frequently Asked Questions

Does creating a Department here automatically update existing Employee records?

No. Existing Employee records that still store department/title as free text are left untouched until the Employees screen (or another module) is updated to reference Organization records directly. Organization's rollout is incremental, module by module.

Can a department be nested more than one level deep?

Yes — Parent Department is self-referencing, so you can build multi-level hierarchies (e.g. Engineering > Product Engineering > Frontend) as deep as your company structure requires.

What does the Level field on a Title actually control?

It's a numeric seniority indicator you define (for example 1 for junior, 2 for mid, 3 for senior) used for sorting and future reporting on career progression. It doesn't drive permissions or approval chains.

Is the Org Chart tab here different from the standalone Org Chart screen?

No — it's the same Org Chart component embedded as a tab for convenience while you're working on Departments, Titles, and Branches. There's no separate logic or separate data behind it.

Can I delete a Department that's still referenced by a Title or an Employee?

Delete always asks for inline confirmation first. Removing a department that other records still point to is a data-integrity concern to consider before deleting — check the Titles tab and Employees for references to a department before removing it.

How many Branches, Departments, or Titles can I create?

There's no fixed limit built into the screen itself; the default sample tenant ships with 15 departments, 18 titles, and 3 branches as a starting reference, and you can add as many as your company structure needs.

Are Document Library files shared with every employee, or restricted?

Documents uploaded to the company-wide library are visible to anyone with access to the Organization screen — typically HR managers. There is no per-file, per-employee visibility control; use it for company-wide references, not confidential per-person records (those belong in Document Entry instead).

Do Leave Rules automatically enforce entitlement limits on leave requests?

Leave Rules define the policy numbers (annual days, carry-over, approval requirement), but Leave Management's request/approval flow is a separate feature — check that screen's own documentation for how entitlements are actually enforced against requests.