Policies
Quotas, monthly or yearly credits, carry-forward, half days, notice and the sandwich rule for each leave type.
Time off, approved and counted right
Handle leave requests, balances and holidays for the team, with manager approval and a who's-out calendar.
Each domain sets its leave types (Casual, Sick, Earned, Comp-off, Unpaid, and Work from home, which does not count against a balance) with a yearly quota, credits upfront, monthly or after the year, a carry-forward cap, half days, minimum notice, most days in a row, a sandwich rule and pro-rata from the joining date. Holidays per leave year start from a 2026 and 2027 Indian list (festivals marked "check date" until confirmed), with optional holidays each person picks up to a limit. A request counts working days without the weekend and holidays, checks notice, overlap and balance, and goes to the person's manager, an editor or the owner; nobody decides their own, and every step is emailed. Balances are a ledger of credits, usage, reversals, adjustments (comp-off) and the year-end carry-forward and lapse, kept by a monthly cron. Today's absentees and a month calendar show who is out, with a secret ICS feed; employees (member role) see only their own leave unless the owner shows them the team calendar. Reports by person, type and month with CSV, joining dates and managers from People (optional), GET /api/v1/absences and /api/v1/balances, webhooks, and Claude to answer an employee's policy question from the configured rules.
What Leave does for you.
Quotas, monthly or yearly credits, carry-forward, half days, notice and the sandwich rule for each leave type.
Requests go to the manager with a balance check, and every step is emailed.
Today's absentees, a month calendar and a calendar feed.
A suggested path for Leave. What you can do depends on your access in the app.
Start from the six ready types and the Indian holiday list.
Set each person's manager and joining date.
Managers approve or reject; balances update on their own.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain sets its leave types (Casual, Sick, Earned, Comp-off, Unpaid, and Work from home, which does not count against a balance) with a yearly quota, credits upfront, monthly or after the year, a carry-forward cap, half days, minimum notice, most days in a row, a sandwich rule and pro-rata from the joining date. Holidays per leave year start from a 2026 and 2027 Indian list (festivals marked "check date" until confirmed), with optional holidays each person picks up to a limit. A request counts working days without the weekend and holidays, checks notice, overlap and balance, and goes to the person's manager, an editor or the owner; nobody decides their own, and every step is emailed. Balances are a ledger of credits, usage, reversals, adjustments (comp-off) and the year-end carry-forward and lapse, kept by a monthly cron. Today's absentees and a month calendar show who is out, with a secret ICS feed; employees (member role) see only their own leave unless the owner shows them the team calendar. Reports by person, type and month with CSV, joining dates and managers from People (optional), GET /api/v1/absences and /api/v1/balances, webhooks, and Claude to answer an employee's policy question from the configured rules.
Employee records belong to People; working time belongs to Timesheets.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
leaves.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.