Settings
Getting Started 3
Employee Essentials 19
My Team 67
Employee Lifecycle 15
Tools 6
Reports 10
Settings 27
Approvals & Access 7
Attendance 55
Leave 14
Daily Attendance 10
Scheduling 7
Reports 10
Settings 11
Payroll 59
Payments & Adjustments 11
Reports 9
Running Payroll 11
Settings 24
Benefits 16
Expenses 10
Invoicing 12
Clients & Templates 5
Invoices 3
Performance 33
Assessments 5
Goals 7
Settings 6
Learning 6
Tasks 21
6 articles in Settings
Activating Task users
Being in KAMI does not put someone in KAMI Tasks. Task access is granted separately, in your main KAMI account — which is why the KAMI Tasks Users page is read-only and why new joiners so often…
Read article →Automations
Automations are the rules that chase things so a person does not have to: a ticket goes blocked and someone is told, a critical ticket sits unassigned and someone is told, a sprint's velocity drops…
Read article →Importing tickets from a spreadsheet
Moving to KAMI Tasks from another tool — or from a planning spreadsheet — does not mean retyping the backlog. The import takes a spreadsheet and turns its rows into tickets.
Read article →Integrations: GitLab, Slack and Claude Code
Integrations connect KAMI Tasks with your development tools so tickets stay in sync automatically — code activity lands on tickets, ticket activity lands in Slack, and an AI assistant can work your…
Read article →Ticket Standards
Ticket Standards are your company-wide rules for how tickets are written — one format for titles, one structure for descriptions, applying to every ticket type in every project. They exist so a board…
Read article →Users and groups
People reach KAMI Tasks through two layers: users — everyone who can be assigned work — and groups, the teams they are organised into. Groups are what projects actually grant access to, which makes…
Read article →