MyCaseNote gives users a self-serve way to enable multi-factor authentication from their profile settings, helping NDIS provider teams strengthen account security without waiting on a manual admin process.
Quick Guide
What to know about multi-factor authentication
Let users enable authenticator-app MFA from their profile settings to add another layer of account protection for sensitive case note workflows.
What self-serve MFA means
Self-serve MFA lets users enable multi-factor authentication for their own account from profile settings. Instead of relying only on a password, users verify with an authenticator-app code before continuing through protected MFA flows.
Give users a way to add MFA when they want extra protection.
Use authenticator-app codes for the second verification step.
Reduce dependence on manual support or admin setup.
Who is this for?
This is for NDIS providers that want stronger account security for people who access case notes, participant records, and sensitive documentation. It pairs naturally with encrypted case notes and staff access control.
Support workers who want additional login protection.
Coordinators who review sensitive participant documentation.
Provider leaders tightening security across documentation workflows.
Why MFA matters for case note software security
Case note software often contains sensitive participant information, so compromised credentials can create serious privacy and operational risk. MFA adds another account-security layer alongside participant data encryption, audit trails, and the broader MyCaseNote security practices.
Help reduce risk when a password is guessed, reused, or exposed.
Add account protection around participant records and case notes.
Support stronger security habits without changing the note workflow.
Product Workflow
How MyCaseNote helps with multi-factor authentication
See how MyCaseNote turns the day-to-day documentation work behind multi-factor authentication into a workflow that is easier for staff to complete and easier for managers to review.
Let users enable MFA from profile settings
Self-serve MFA gives users a direct path to strengthen their own account. In MyCaseNote, eligible users can go to profile settings and start authenticator-app setup without asking an administrator to configure it for them.
Start MFA setup from the user profile.
Scan a QR code or enter the setup secret in an authenticator app.
Verify the code to complete enrollment.
How MFA supports secure NDIS documentation workflows
Limit record visibility with roles and assignments.
Keep sensitive record activity easier to review.
Support stronger security without extra admin overhead
Security controls work best when teams can actually adopt them. Self-serve MFA lets users take action on account protection while managers keep focusing on documentation quality, review workflows, and participant support.
Avoid manual account-by-account MFA setup.
Let security-conscious users enable MFA when ready.
Keep documentation workflows familiar for frontline teams.
FAQ
Common questions about self-serve mfa for ndis provider teams
Quick answers to the questions providers usually ask before changing their documentation workflow.
Can all users enable MFA in MyCaseNote?
Yes. MyCaseNote supports self-serve MFA so regular users can enable authenticator-app MFA from their profile settings when the feature is available for the environment.
What kind of MFA does MyCaseNote support?
MyCaseNote supports authenticator-app MFA using time-based verification codes.
Does MFA replace role-based access control?
No. MFA protects the user account sign-in flow, while role-based access controls what records and actions a user can access after signing in.