> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ontime.hosai.app/llms.txt
> Use this file to discover all available pages before exploring further.

# The employee record

> A tour of the eight tabs on an employee's file and what each one is for.

export const PermissionNote = ({perm}) => <Info>
    Requires the <code>{perm}</code> permission. Ask your administrator if an
    action described here is missing from your screen — see
    [Roles & permissions](/help/concepts/roles-and-permissions).
  </Info>;

<PermissionNote perm="employee:read" />

Opening someone from the directory gives you their whole file: a header with their identity and current status, and eight tabs.

## The header

Name, designation, employee code, joining date, status, location, who they report to, and their compensation. Everything else is a tab below it.

## The tabs

<AccordionGroup>
  <Accordion title="Profile" icon="user">
    Personal details — name, date of birth, gender, contact, address — and identity and bank information: PAN, Aadhaar and bank account (masked), Provident Fund and Employees' State Insurance numbers.

    Editable with `employee:write`.
  </Accordion>

  <Accordion title="Work" icon="briefcase">
    Designation, department, location, shift template, manager and employment type. This is where the manager link — the one approvals route on — is set.
  </Accordion>

  <Accordion title="Attendance" icon="clock">
    Their month calendar with a month-to-date summary, month navigation, and a read-only day detail showing the shift window, worked bands, punch trail and location.

    Two write actions live here: a **manual punch** at an explicit timestamp, and a **bulk range override** applying a status across dates. Both need `attendance:write` and both are audited. See [Manual punches and overrides](/help/attendance/manual-punches-and-overrides).

    <Note>
      The day drawer is inspect-only — there is no per-day override control inside it. Use the range form for a single day.
    </Note>
  </Accordion>

  <Accordion title="Leave" icon="palmtree">
    Balance tiles per leave type and full leave history, with year-so-far and approval-flow panels. **Apply on behalf** files a request against this employee — see [Applying for leave](/help/leave/applying).
  </Accordion>

  <Accordion title="Compensation" icon="indian-rupee">
    Current salary structure and the immutable revision history. Filing a revision needs `payroll:write`. See [Compensation](/help/payroll/compensation).
  </Accordion>

  <Accordion title="Documents" icon="folder">
    The employee's document vault, grouped by category, with upload, verify, delete and request-missing. See [Documents](/help/people/documents).
  </Accordion>

  <Accordion title="Devices & sessions" icon="smartphone">
    Enrolled mobile and biometric devices, and active sign-in sessions — with revoke for each, and sign-out-everywhere. See [Sessions and devices](/help/admin/sessions-and-devices).
  </Accordion>

  <Accordion title="Audit" icon="scroll-text">
    Everything that has been done to this employee's record: who, when, what changed. Faceted by category and period, with CSV export. See [Audit log](/help/admin/audit-log).
  </Accordion>
</AccordionGroup>

## Permissions across the tabs

Reading the record needs `employee:read`. Individual tabs then gate on their own key — `attendance:write` for the punch actions, `payroll:write` for a revision, `document:write` for uploads, `audit:read` for the audit tab. A viewer without a tab's permission does not see that tab's write controls.

## Scope

`employee:read` lets you open employee records. **Which** records depends on your scope: a manager sees their direct reports, an `hr:approve` holder sees the organization. Some fields are additionally redacted for viewers outside scope even on records they can open.

See [Roles & permissions](/help/concepts/roles-and-permissions).