AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus
Skip to documentation
Docs
Back to Atlas

Start here

  • Overview

Developer

  • REST API guide
  • Authentication
  • API reference
  • MCP (AI agents)
  • SDKs
  • Quick actions

Webhooks

  • Overview
  • Quickstart
  • Events
  • Payloads and headers
  • Security and signing
  • Delivery and retries
  • Managing via API

Connect

  • Connectors
  • Integrations

Product

  • Collaboration and chat

Reference

  • Glossary
  • Keyboard shortcuts
  • Module reference
Module reference

Module guide

People

The employee record and everything that hangs off it, from hiring to payroll.

Open module/people
hradmin

Overview

People is the human resources module. It holds the employee record and the things that attach to it: departments and the org chart, attendance and holidays, leave requests and their approvals, hiring from an opening through to an offer, onboarding a new joiner, performance, and pay runs. The overview opens with the numbers a manager needs before anything else, which are headcount, who joined recently, who is away today, what leave is waiting on an approval, which openings are still unfilled, and when the next pay run falls. It is one module rather than several because an employee record that disagrees with the rota, the leave balance and the payroll is worse than no record at all.


Highlights

The capabilities worth knowing before you dive in.

  • An overview that opens with headcount, recent joiners, who is away today, leave awaiting approval, open roles and the next pay run
  • Employee records, departments and an org chart built from them
  • Attendance and holidays, with leave requests and their approval path
  • Hiring from an opening to an offer, and onboarding for the person who accepts
  • Performance, and pay runs, reading the same employee record as everything else

Important to know

Limits, permissions, and sharp edges to keep in mind.

  • People is a premium module and the whole route is gated on it. Without the entitlement the screens are closed rather than empty.
  • Employee data is personal data, and much of it is sensitive. Access is by role, and what one person can see is not what another can.
  • A leave request changes an approved balance only once it is approved. A pending request is not a booked absence.
  • Departments and the org chart are built from the employee records. Correcting the chart means correcting the record it came from.
  • A pay run reads the employee record at the time it runs. Correcting a record after a run does not retrospectively change that run.

How to use it

The primary workflow, start to finish.

  1. 1Open People. The overview answers the questions a manager asks first.
  2. 2Work from the section you need: employees and departments for the record, attendance and leave for who is where, hiring and onboarding for who is arriving.
  3. 3Approve or decline the leave requests waiting on you. The balance changes on approval, not on request.
  4. 4Read the org chart when you need the shape of the organisation, and correct it by correcting the employee record behind it.
  5. 5Review the next pay run before it runs, because a correction afterwards does not change a run that has already happened.

FAQ

Why can I not open People?
It is a premium module and the route is gated on the entitlement. Without it the screens do not load at all rather than loading empty.
Why can I see less than my colleague?
Because employee data is personal and often sensitive, so access is by role. Seeing less is the system working rather than a fault.
Can I change my exit interview after I have sent it?
Not yourself. The self-service exit interview is submitted once. Opening it again shows you the date you sent it rather than an empty form, and the answers themselves are held for HR rather than shown back to you, because the notes are part of the offboarding record. Ask HR to revise them.
When does a leave request affect the balance?
On approval. A pending request is a request, and treating it as booked would let a balance go negative on approvals that never came.
I corrected a record after payroll ran. Is the run updated?
No. A pay run reads the record as it stood when it ran, which is what makes it auditable. A correction is applied to the next run or handled as an adjustment.
The org chart is wrong. Where do I fix it?
On the employee record. The chart is derived from the records, so editing the chart directly would let the two disagree.

Automate this module

Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
All modules
Was this page helpful?

On this page

  • Overview
  • Highlights
  • Important to know
  • How to use it
  • FAQ