Platform basics · Article 1 of 6
What is Navigator?
Navigator is Kismet's internal platform for managing NDIS plan management operations. It's the central hub your team uses to manage participants, process invoices, track budgets, coordinate with suppliers, and stay on top of day-to-day work — all in one place.
What your team does in Navigator
It's accessed at kismet.healthcare/accounts/ and is used exclusively by internal staff. Participants and suppliers have their own separate portals.
As a plan management organisation, your team sits between NDIS participants, the suppliers delivering their supports, and the NDIS itself. Navigator is built to support every part of that role:
- Receiving and processing invoices from suppliers on behalf of participants
- Validating claims against each participant's support plan and budget
- Submitting claims to the NDIS through PRODA
- Onboarding new participants and setting up their records, plans, and contacts
- Monitoring budgets and alerting participants when funds are running low
- Managing supplier relationships including service agreements and claim rules
- Communicating with participants, contacts, and suppliers via email, phone, and SMS — all logged in one place
The core things you'll work with
Navigator is built around a handful of key concepts. Once you understand these, the rest of the platform makes sense:
| Term | What it means |
|---|---|
| Customer | An NDIS participant your organisation manages. Every piece of work in Navigator connects back to a customer. |
| Contact | A person associated with a customer — a family member, support coordinator, or key worker. Contacts often approve invoices on a customer's behalf. |
| Supplier | A service provider delivering supports to a customer. Suppliers submit invoices for payment. |
| Invoice | A claim submitted by a supplier for services delivered. Your team validates, approves, and submits these to the NDIS. |
| Support plan | A customer's NDIS plan, including their allocated budgets across support categories (Core, Capital, Capacity Building). |
| Task | A unit of work in your queue. Everything from processing an invoice to onboarding a new participant starts and ends as a task. |
What a typical day looks like
Your task queue is your primary work surface in Navigator. When you log in, you'll see your assigned tasks — sorted by priority, due date, and status.
Tasks are created in a few ways:
- Automatically — when an email arrives, an invoice is received, a budget threshold is hit, or an onboarding step is triggered
- Manually — when a team member creates a task directly
From there, a task might involve reviewing an AI-extracted invoice, chasing a missing service agreement, processing a budget alert, or completing a step in a participant's onboarding checklist. Every action, note, and communication is logged against the task for full traceability.
Where your work lands
Once a task is tagged, it lands in one of a handful of places. These are the main surfaces your team works from day-to-day:
- Triage and categorise
- Archive if no action needed
- Assign where specific
- My active tasks
- Due today
- Awaiting follow-up
- All team tasks
- Filterable by tag
- Re-assign or bulk action
- Approval not sent
- Pending approval
- Approved
- Rejected
- Cancelled
- Paused
- NDIS claim submitted
- NDIS claim rejected
- NDIS claim paid
- Paid
- Refund requested
- Refunded
- Review required
- Active
- Inactive
- Prospect
- Nominees
- Support coordinators
- Family / other
- Approved / active
- Bank verification pending
- Inactive
- Bank transfer extracts
- NDIS submission extracts
- Plan management fees
- Dashboard reports
- Exports (CSV)
- Fees & revenue
How Navigator fits into the broader Kismet platform
Navigator is one part of the wider Kismet ecosystem:
- Participants have their own portal where they can view their support plan, budgets, invoices, and monthly statements
- Suppliers have a provider portal to view service agreements, submit invoices, and track payments
- Navigator is the operational layer — the internal tool your team uses to manage everything happening across both of those portals