Master Data
Detailed field and column guide for branches, departments, designations, shifts, holidays, and leave types.
Workflow
- LocationsAdmin / HR: Create branches and departments.
- JobsAdmin / HR: Create designations and manager structures.
- Time policyAdmin / HR: Create shifts, grace rules, holidays, and leave types.
- MaintainAdmin / HR: Deactivate old records instead of deleting historical values.
| Stage | Actor | Action | Result |
|---|---|---|---|
| Locations | Admin / HR | Create branches and departments. | Employees and reports can be grouped. |
| Jobs | Admin / HR | Create designations and manager structures. | People records have correct roles in the organization. |
| Time policy | Admin / HR | Create shifts, grace rules, holidays, and leave types. | Attendance and leave calculations have policy context. |
| Maintain | Admin / HR | Deactivate old records instead of deleting historical values. | Past attendance and payroll remain readable. |
Organization Map prompt import
Builds draft organization nodes from a guided or AI assisted prompt, shows a preview drawer with a summary, and the Apply Selected action applies only selected valid rows through the organization map service.
| Essential field | Plain meaning | Example | Required / notes |
|---|---|---|---|
| Prompt | Plain text describing regions, stores, departments, teams, positions, shifts, policies, or manager scopes. | Departments: Sales, HR |
Preview before create. |
| Preview items | Draft nodes with client id, type, name, code, parent, attributes, source text, status, and messages. | draft_1 / department / Sales |
Invalid parent relationships are blocked. |
| Summary drawer | Counts by type and status. | department: 2 / ready: 2 |
Helps review large prompts. |
Branch form
Defines physical or operational locations used by employees, shifts, holidays, filters, and reports.
| Essential field | Plain meaning | Example | Required / notes |
|---|---|---|---|
| Name | Branch display name. | Head Office |
Required. |
| Address / city | Where the branch is located. | Karachi |
Used for reference and reports. |
| Manager | Person responsible for the branch. | Ayesha Manager |
Optional. |
| Active | Whether the branch can be selected. | On |
Turn off instead of deleting if used historically. |
| Notes | Extra context. | Primary office |
Optional. |
Department and designation forms
Departments group teams; designations define job titles inside or across departments.
| Essential field | Plain meaning | Example | Required / notes |
|---|---|---|---|
| Department name | Team or function name. | Operations |
Required. |
| Department code | Short identifier. | OPS |
Required. |
| Designation name | Job title. | Support Executive |
Required. |
| Linked department | Team this title belongs to. | Operations |
Recommended. |
| Description | What this department/title does. | Customer operations team |
Helpful for admins. |
Shift form
Defines working time, branch assignment, grace period, night shift behavior, and shift notes.
| Essential field | Plain meaning | Example | Required / notes |
|---|---|---|---|
| Name | Readable shift label. | General 9 to 6 |
Required. |
| Code | Short unique shift code. | GEN-9 |
Required. |
| Branch | Branch this shift belongs to. | Head Office |
Optional depending on policy. |
| Start / end time | Expected work window. | 09:00 / 18:00 |
Required. |
| Grace minutes | Minutes allowed before late status. | 15 |
Required for attendance evaluation. |
| Night shift | Whether shift crosses midnight. | No |
Important for checkout logic. |
Holiday form
Defines paid, branch-specific, national, or company holidays used by attendance and leave logic.
| Essential field | Plain meaning | Example | Required / notes |
|---|---|---|---|
| Holiday name | Label shown in calendars and attendance. | Labour Day |
Required. |
| Holiday date | Date the holiday occurs. | 2026-05-01 |
Required. |
| Branch | Branch affected by the holiday. | All branches |
Blank usually means all. |
| Paid | Whether it counts as paid time. | Yes |
Important for payroll policy. |
Leave type form
Defines leave categories, yearly allowance, approval behavior, paid/unpaid effect, attachments, and half-day support.
| Essential field | Plain meaning | Example | Required / notes |
|---|---|---|---|
| Name / code | Leave label and identifier. | Annual Leave / ANNUAL |
Required. |
| Carry forward limit | Unused days allowed next year. | 5 |
Policy decision. |
| Paid | Whether leave is paid. | Yes |
Affects payroll interpretation. |
| Requires attachment | Whether file proof is needed. | No |
Useful for sick leave. |
Master data listing table
Displays records for the selected master-data type and lets admins filter, edit, or deactivate them.
| Column | What it means | Where it comes from | Example interpretation |
|---|---|---|---|
| Name | Readable label shown in dropdowns. | master table. | General 9 to 6. |
| Code | Short stable identifier. | master table. | GEN-9. |
| Linked records | Parent or related records. | branch/department relationship. | Shift belongs to Head Office. |
| Policy values | Type-specific values like time, allowance, or date. | selected model fields. | Grace minutes: 15. |
| Active | Whether it can be selected in new records. | is_active field. | Inactive values stay in history. |
| Status | Current workflow state for the row. | The record status field or computed workflow state. | Pending means someone still needs to act. |
- Open or edit the record when permission allows it.
- Filter the list without losing the current page context.
- Use status badges to decide which item needs attention first.
Main docs show essential fields only. Open Documentation Coverage for every detected source field, action, column, route hint, controller hint, and test hint.