Last updated 12 Oct 2026
Enterprise
Control and evidence for larger NDIS providers
For organisations with many sites, teams and approvers: decide who sees what, prove who changed what, and connect Autonomy Care to your finance and reporting systems.
Autonomy Care gives larger and multi-site NDIS providers the controls an organisation needs: custom roles and permissions, single sign-on with Microsoft Entra ID or Google Workspace, a two-step sign-in policy, activity logs that can't be edited, scheduled reports, licensing by module, a public API with signed webhooks, and finance and payroll connections.
What do larger providers get?
Everything in a standard account, plus the controls an organisation with several sites and teams relies on.
Roles and permissions
Build your own roles from fine-grained permissions, grouped by module. Support workers see the care information they need, not plans or funding.
How access worksSingle sign-on
Staff sign in with Microsoft Entra ID or Google Workspace. Require it for admins or for all staff.
Two-step sign-in policy
Off, optional, required for admins or required for everyone. An admin can reset it for a staff member.
Activity logs that can't be edited
Who did what, when and from where. Logs are hash-chained, checked every day and can be exported.
Scheduled reports
Send a report daily, weekly or monthly to up to 20 staff. Each person's permissions are checked again on every send.
About reportsLicensing by module
Your licence sets which modules your organisation uses. Add-ons such as the public API stay off until you choose them.
Public API and webhooks
Scoped API keys, documented endpoints and signed webhooks for your own tools. An add-on.
About the APIFinance and payroll connections
Invoices to Xero, MYOB or QuickBooks Online, approved hours to Xero Payroll, MYOB or Employment Hero Payroll, and contacts to HubSpot.
About integrationsSeveral organisations, one person
Staff who work for more than one organisation on Autonomy Care switch between organisations. Each organisation's records stay separate.
How do roles and permissions work?
Access is controlled by roles. Each role is built from fine-grained permissions, grouped by module, and you can create your own roles for each team.
- Least access by default for workers. Support workers see support needs, goals, medicines, alerts, contacts and handovers for the participants they support. They don't see plans, funding or plan managers.
- Sensitive actions need their own permission. For example, pay figures, exports, connecting integrations and creating API keys are separate permissions you give only to the roles that need them.
- One organisation per request. Each request is tied to one organisation, taken from the sign-in itself.
- Modules you don't have stay hidden. Screens for modules outside your licence are hidden, and the server refuses their requests.
How does single sign-on work?
Single sign-on uses OpenID Connect with Microsoft Entra ID or Google Workspace. An admin adds your organisation's connection in Settings, then Security, lists your email domains, and runs Test connection.
- Only existing staff and admins can sign in this way. Single sign-on never creates new accounts.
- Require it for admins or for all staff. Owners keep a password and two-step sign-in as a way in if your identity provider is down.
- Turning the requirement on needs a passing connection test, and signs out password sessions for the people it now covers.
- If your identity provider reports that it checked a second factor, Autonomy Care doesn't ask for its own code. Otherwise your two-step policy applies.
- Every sign-in attempt, successful or not, is recorded and shown to admins.
Single sign-on isn't available in the mobile app or for families, and SAML isn't supported. Support workers sign in to the app with a password, plus two-step sign-in if your policy requires it.
Can we prove who changed a record?
Yes. Every change in your organisation's account is written to the activity log: who, what, when and from where. Sign-ins are logged too, and the Document Centre logs every view and export of a record.
- The database refuses any change or deletion of these logs, apart from the purge of rows older than 7 years.
- Activity logs are hash-chained for each organisation, so a changed or missing row breaks the chain. The chain is checked every day.
- Admins can filter the logs and export them for an auditor or an investigation.
- Changes made through the API name the API key that made them.
Controls at a glance
| Control | Your choices | Good to know |
|---|---|---|
| Two-step sign-in | Off, optional, required for admins or required for everyone | Uses an authenticator app with one-time recovery codes. It applies from each person's next sign-in. |
| Single sign-on | Microsoft Entra ID or Google Workspace, your email domains, and whether it's required for nobody, admins or all staff | OpenID Connect only. Owners keep a password and two-step sign-in. |
| Roles | Your own roles, built from fine-grained permissions | Support workers see care information only, not plans or funding. |
| Activity and sign-in logs | Filter and export | Can't be edited or deleted. Kept for at least 7 years. |
| API keys | The scopes each key may use, and an optional expiry date | Shown once and stored only as a hash. Revoking a key stops it at once. |
| Webhooks | The events each webhook receives | Signed with HMAC-SHA256. A failed delivery is tried 8 times over about 24 hours. |
| Scheduled reports | Daily, weekly or monthly, in any Australian time zone, to up to 20 staff | Reports with personal information go as an expiring download link, never as an attachment. |
| Licence modules | The modules your organisation uses, and add-ons | The core is always included: participants, staff, roles, notes, leave, settings and logs. |
Built for each team in a larger organisation
Every team works from the same participant record, with access set by its role.
Owners and executives
An executive summary report you can schedule, dashboards, and Signals that flag what needs attention.
About dashboardsIT and security
Single sign-on, the two-step policy, roles, API keys and webhooks, and activity logs you can export.
About security and privacyFinance
Invoices, NDIA bulk payment request files and remittance matching, with cost centres by house, region or support category in your ledger.
About billing and claimsPayroll
SCHADS pay worked out on timesheets, a setup check before each export, and approved hours sent to Xero Payroll, MYOB or Employment Hero.
About payrollQuality and compliance
Incident deadlines, complaints, corrective actions and the risk register, with registers you can export for an auditor.
About incidentsRostering and coordination
Rosters checked against your eligibility rules on every save, open shifts and worker matching across sites.
About rosteringHR and training
Credentials and screening checks that feed the roster, and a training matrix you can export.
About staff and credentialsHouse and site leads
SIL house rosters, staffing gaps and handovers for each house.
About SIL houses
How does it support the NDIS Practice Standards?
Autonomy Care keeps the records an auditor asks for in one place, so you can show the evidence behind your policies:
- Incidents with NDIS Commission deadlines worked out and reviewers alerted before and after them. You notify the Commission yourself and record the reference.
- Complaints, feedback, corrective actions and a risk register with owners and review dates.
- Restrictive practice use records.
- Policies with staff acknowledgements, and document control.
- Credentials and screening checks: an expired NDIS Worker Screening clearance blocks the shift.
- A training matrix and competencies, with evidence.
- Incident, complaints and corrective action registers that export as CSV.
How is participant information protected?
- NDIS numbers, dates of birth, medication details, incident narratives, progress note text and complaint text are encrypted before they reach the database, with their own key.
- Connection tokens for Xero, MYOB, QuickBooks, HubSpot and Employment Hero are stored encrypted and never sent to the browser.
- Shift text messages never include participant names or addresses, and push notifications show a general message only.
- Webhook payloads carry ids and a few non-identifying fields only, never names, notes or health information.
Where something isn't decided yet, such as the hosting region, we say so on our security and privacy page.
What does implementation look like?
A person reviews each application before your account is created. Setup emails arrive on the day your account is created and on days 1, 3 and 7. How long the whole switch takes depends on your data and your pay cycle.
Get started or book a demo
Tell us about your organisation and how many sites and staff you have.
First sign-in
The owner gets a welcome email with a link to set their password. Set your two-step policy and, if you use it, single sign-on.
Set up the organisation (day 1)
Organisation details, roles, the price guide and support items. Import staff from a CSV file; you see a preview and any problems before anything is saved.
Rosters and the worker app (day 3)
First shifts, the rostering rules you want checked, and the mobile app for support workers.
Billing and claims (day 7)
Invoices from completed shifts and NDIA bulk payment request files.
Connect finance and payroll
Connect your accounting and payroll systems, check the suggested mappings, and run the payroll setup check before your first export.
Go live at the start of a cycle
Switch at the start of a pay and claim cycle, run both systems side by side for a short time, and keep the old one until remittances are reconciled.
What we do and don't offer yet
It does
- Single sign-on with Microsoft Entra ID and Google Workspace
- A two-step sign-in policy for the whole organisation
- Custom roles from fine-grained permissions
- Activity logs that can't be edited, checked every day
- Licensing by module, with add-ons
- A public API and signed webhooks, as an add-on
It doesn't
- No SAML or SCIM, and no new accounts created at first sign-in
- No single sign-on in the mobile app or for families
- No report builder inside Autonomy Care: use the exports or the API
- Doesn't submit claims to the NDIA: you upload the bulk payment request file
- We don't hold security certifications such as ISO 27001 or SOC 2
Questions from larger providers
Can staff sign in with Microsoft or Google?
Yes. Single sign-on works with Microsoft Entra ID and Google Workspace using OpenID Connect. Your organisation can require it for admins or for all staff. The mobile app doesn't support single sign-on; workers sign in with a password, plus two-step sign-in if your organisation requires it or the worker turns it on.
Do you support two-step sign-in?
Yes. Staff can use an authenticator app with one-time recovery codes. Your organisation can make it optional, required for admins, or required for everyone.
Can we see who accessed or changed a record?
Yes. Activity logs record who did what and when, and can be exported. Document records also log every view and export. Logs can't be edited or deleted, and are hash-chained so tampering can be detected.
What's included for every provider?
Every account has the core: participants, staff, roles and permissions, progress notes, leave, settings and activity logs. New accounts also have the standard modules switched on, from rostering and SIL houses to billing, payroll and the Family portal. The public API and AI note summaries are add-ons that stay off unless chosen.
How are API keys stored?
Keys are shown once and stored only as a hash. They can have an expiry, can be revoked, and show when they were last used.
Are there rate limits?
Yes, 120 requests a minute per key, with rate limit headers in each response.
What if our webhook endpoint is down?
Deliveries are retried 8 times over about 24 hours. After that the webhook is turned off and your admins are told. A 30-day delivery log lets you resend.
Can we connect a system that isn't listed?
The public API and webhooks add-on lets your developers or tools like Zapier connect other systems.
Who can receive a report?
Up to 20 staff per schedule. Each recipient's permissions are checked every time it is sent.
Can we import our staff list?
Yes. Staff can be imported from a CSV file. You see a preview and any problems before anything is saved.
Will software make us compliant?
No. Software helps you keep and find evidence. Compliance comes from your practices, policies and people.
Can we sign up and start straight away?
Not yet. Each application is reviewed by a person before an account is created. This helps us set up your account properly and check we are a good fit.
Related
Large providers
What gets in the way for providers with many teams and sites
For large providersSecurity and privacy
Encryption, logs, sign-in and what isn't decided yet
About security and privacyTrust centre
Security, privacy, AI and accessibility in plain words
Visit the Trust centreSwitching NDIS software
Steps to move without losing a claim cycle
Read the switching guideXero integration
Step by step: invoices, payments and payroll
About the Xero integrationPublic API and webhooks
Keys, scopes, endpoints and signed webhooks
About the API
Plan your rollout with us
Book a demo for your leadership, finance and IT teams. We'll show the controls with your own questions.