Employee records
Work details for the directory; private details only HR and the person can see.
Your team, from the first day to the last
Keep the team directory, employee records, onboarding and exits for each business in one place.
Each domain keeps an employee record per person: photo link, work email, phone, title, department, location, manager, type (full-time, part-time, intern, contractor), joining, probation and contract end dates, status, custom fields and an ID series like EMP-0001. Private details (date of birth, personal email, emergency contact, address) sit in their own table that only the owner, HR and the person can read; the directory and the API never read it. The org chart is the reporting tree, with departments, their heads and headcount. Onboarding and offboarding checklists start from editable templates with tasks for HR, the manager or the person, due a number of days from the joining date or the last day. Exits record the last day, reason, full and final settlement with UTR, assets returned and rehire. Documents are links with a visibility and an expiry date. A daily 10:00 IST digest to HR lists expiring documents and contracts, probation ends, last days, overdue tasks and the week's birthdays and work anniversaries. CSV import (also from the Careers export) and export, GET /api/v1/people for Leave, Timesheets and Assets, webhooks, and Claude for an onboarding plan and a welcome note.
What People does for you.
Work details for the directory; private details only HR and the person can see.
The reporting tree, departments and headcount.
Onboarding and offboarding tasks, exits with full and final settlement, and dated documents.
A suggested path for People. What you can do depends on your access in the app.
Add people one by one or import a CSV.
Let employees sign in to see the directory and edit their own profile.
The daily HR digest lists what needs attention.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain keeps an employee record per person: photo link, work email, phone, title, department, location, manager, type (full-time, part-time, intern, contractor), joining, probation and contract end dates, status, custom fields and an ID series like EMP-0001. Private details (date of birth, personal email, emergency contact, address) sit in their own table that only the owner, HR and the person can read; the directory and the API never read it. The org chart is the reporting tree, with departments, their heads and headcount. Onboarding and offboarding checklists start from editable templates with tasks for HR, the manager or the person, due a number of days from the joining date or the last day. Exits record the last day, reason, full and final settlement with UTR, assets returned and rehire. Documents are links with a visibility and an expiry date. A daily 10:00 IST digest to HR lists expiring documents and contracts, probation ends, last days, overdue tasks and the week's birthdays and work anniversaries. CSV import (also from the Careers export) and export, GET /api/v1/people for Leave, Timesheets and Assets, webhooks, and Claude for an onboarding plan and a welcome note.
Hiring up to the offer belongs to Careers; sign-in belongs to Auth; leave belongs to Leave.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
people.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.