> For the complete documentation index, see [llms.txt](https://docs.inify.nafalabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inify.nafalabs.com/introduction.md).

# Introduction

## Selamat Datang di Dokumentasi Inify

Inify adalah solusi HR & Absensi digital yang membantu bisnis mengelola kehadiran, cuti, shift, dan data karyawan secara real-time. Dokumen ini akan memandu Anda dalam menggunakan fitur-fitur Inify, baik sebagai Owner, Admin, maupun Karyawan.

### 🔗 Tautan Cepat

* [Aplikasi Web](https://app.inify.nafalabs.com)
* [Daftar Akun Baru](https://app.inify.nafalabs.com/register)
* [Daftar Free Trial](https://app.inify.nafalabs.com/demo/register)
* [Hubungi Support](mailto:support@inify.nafalabs.com)

### Fitur Utama

* ✅ **Absensi Real-time**: Clock-in/out dengan validasi lokasi & wajah.
* ✅ **Manajemen Cuti**: Pengajuan dan persetujuan cuti online.
* ✅ **Shift Kerja**: Penjadwalan shift yang fleksibel.
* ✅ **Laporan Otomatis**: Rekap absensi dan kinerja karyawan.
* ✅ **Multi-Lokasi**: Pantau absensi karyawan di berbagai cabang atau lokasi kerja dalam satu sistem terpusat.
* ✅ **AI Generatif**: Asisten AI cerdas untuk membantu generate laporan, analisis data karyawan, dan rekomendasi keputusan HR secara otomatis.

> **Catatan:** Untuk uji coba gratis selama 7 hari (maksimal 5 karyawan), silakan daftar melalui halaman Demo Register.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.inify.nafalabs.com/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.