Getting started & product overview · Lumin Connect
What is Lumin Connect?
Last updated 28 July 2026
Lumin Connect is the integration layer that links Lumin to the other systems an organisation already uses — care management software, maintenance systems, calendar systems, identity providers, and more. It's how Lumin fits into an existing operational stack without forcing operators to switch tools or work in two places. Under the hood, Lumin Connect is powered by Workato, an enterprise-grade integration platform — which is what makes the breadth of connectors possible.
Who Lumin Connect is for
- Villages using established systems for maintenance, bookings, resident records, or staff identity
- Care providers running care management software (AlayaCare, AutumnCare, iCareHealth, etc.) — see the separate article on Lumin Connect for care professionals
- Aged care facilities with clinical care management systems
- Multi-site operators needing consolidated data and identity across sites Individual customers don't typically interact with Lumin Connect directly. It's an operator-side capability.
What it does
Lumin Connect handles the bidirectional flow of information between Lumin and other systems: people data (adding, updating, removing residents/participants in both systems); schedule data (appointments, events, reminders flow into the resident-facing surface); activity events (alerts, check-ins, communications flow into the operator's existing record); identity (staff use their existing work login rather than a separate Lumin password); maintenance (requests submitted on the CareHub flow into the operator's existing maintenance system).
Common integrations
Lumin Connect has pre-built connectors for care management software (AlayaCare, AutumnCare, iCareHealth, others); identity providers (Microsoft 365, Google Workspace, Okta); business and analytics systems (Salesforce, Dynamics 365, Power BI); telehealth (Coviu); cloud infrastructure (AWS, Microsoft Azure); maintenance management (common village maintenance systems); organisation calendar systems (Google Calendar, iCloud and similar) — one-way, reading events into Lumin, scoped per organisation; hospital systems (selectively, scoped per hospital pilot). For systems without a pre-built connector, custom integration is possible — typically scoped as a small project. A note on calendars. The operator-side calendar connector above is a different thing from a resident or Supporter linking their own personal Google or iCloud calendar to a CareHub. That personal calendar sharing isn't currently available — see the separate article on calendar sharing. What Lumin Connect does is read events from an organisation's own calendar system, where that's been scoped for the client.
Why this matters
Without Lumin Connect, staff enter the same information into Lumin and into the operator's existing system. Information drifts between systems. Reports and audit trails are split. Adoption is slowed. With Lumin Connect, staff work in their existing tools and Lumin reflects the activity. Single source of truth is preserved. Reports stay in the right place. Adoption is smoother because the platform fits in, not on top.
What it doesn't do
Lumin Connect is an integration layer, not a replacement layer. It doesn't replicate clinical records inside Lumin. It doesn't synchronise billing or financial data. It doesn't manage care plans or clinical decision support. It doesn't connect to ad-hoc third-party apps without a deliberate integration.
Getting started
Lumin Connect is part of the Enterprise plan and available as a module on other plans. Contact Lumin Support to identify systems to integrate, scope the integration (which data, which direction, what events), pilot with a small cohort (10–30 users), then roll out broadly. Integration projects typically take 2–8 weeks, depending on complexity.