Employee records
Every employee is one record, split into sections that save independently — so HR fills a profile in as the paperwork arrives instead of fighting one giant form. Identity numbers, bank details and salary figures are encrypted in the database, and every change lands in the activity log.
- Sectioned profile, saved per section
- Documents attached to the record
- Custom fields per organization
- Admin-managed lookups, not hard-coded enums
- Identity & bank data encrypted at rest
- Full change history
Org structure
One organization can hold several legal companies that share the same catalogs — units, departments, titles, projects — so a group standardizes once and every entity inherits it. New organizations start from a ready-made catalog and tune it in a setup wizard on first login.
- Multi-company under one organization
- Shared units, departments, titles, projects
- First-login setup wizard
- Ready-made lookup catalog to start from
Positions & pay
Roles and pay are kept as history, never overwritten. A promotion is a new position with a start date; a raise is a new compensation entry with its effective date. Forward-dated changes take effect on their day, and an employee can hold more than one position across group companies with one marked as default.
- Effective-dated position history
- Compensation & attendance-fee history
- Forward-dated promotions and transfers
- Multiple concurrent positions, one default
- Salary amounts encrypted at rest
Time & leave
Admins define workweek plans and leave policies — types, rules, allowances — and Atlas does the arithmetic. Employees request, managers approve through the chain you configured, and balances, the calendar and the reports update on their own. Planned and pending days are held against the allowance so nobody is approved into a negative balance by accident.
- Leave policies with types and rules
- Balances that account for planned and pending days
- Workweek plans per employee, with history
- Team calendar with holidays per department
- Leave balance and leave reports
Approvals, expenses & advances
Define an approval chain once — "Software lead approval", "Finance sign-off" — and attach it per department and per module. The same chain can approve leave for the dev team and their expense receipts. Expenses carry receipts and categories; advances and visa requests run through the same machinery.
- One catalog of approval chains, reused everywhere
- Attach chains per department and module
- Expense receipts and categories
- Salary advances with approval
- Visa requests with reminders
Assets & inventory
Laptops, phones, cards, keys: every asset is one record with a movement history. The warehouse tracks shelves, stock entries, exits and returns; the employee side shows each person exactly what is assigned to them. When someone leaves, the return list writes itself.
- One record per asset, with movements
- Shelf management, entry, exit and return
- "My assets" view for every employee
- Assignment history per person
Performance
Performance reviews are scheduled from the hire date at the interval you choose, and the reminder email goes out a week before — once, not every day. Managers see who is due; HR sees the whole calendar.
- Review cadence from hire date
- Scheduled reminder emails
- Reviews recorded on the employee
Reporting & audit
Reports read the same records the rest of Atlas writes, so headcount, structure and leave figures are never a day behind. The activity log keeps who changed what and when, across every module.
- Headcount and structure reports
- Leave balance and usage reports
- Organization-wide activity log
AI employee assistant
Atlas exposes a scoped API for the Rakita employee assistant: it acts as the signed-in employee, sees exactly what that employee may see, and nothing more. Leave balance, who is out this week, which assets are on my name — answered in chat, without an HR ticket.
- Answers from the employee's own record
- Same permissions as the signed-in user
- Part of the Rakita platform, one login