Faithlife compliance, automated for SOC 2, ISO 27001 & Cyber Essentials
OneClickComply connects to Faithlife through the OneClickComply Companion, our AI browser agent, and checks how it is configured against SOC 2, ISO 27001, Cyber Essentials and NIST CSF. Checks include: security awareness training assigned to all staff, completion tracked and chased and training records retained as evidence. Every result is stored as audit evidence, so there are no screenshots to collect.
SOC 2 · ISO 27001 · Cyber Essentials · NIST CSF
- Set up in minutes
- No API keys or extra logins
- Evidence collected continuously
- Built for UK teams
Continuous control checks
What OneClickComply checks in Faithlife
Security awareness training is required by almost every framework. Completion records are the evidence auditors ask for.
Security awareness training assigned to all staff
Completion tracked and chased
Training records retained as evidence
See it work
Watch OneClickComply check Faithlife
The Companion, our AI browser agent, opens Faithlife with the access you already have, reads the settings that matter, tests them against your controls and files the result as evidence.
Faithlife admin
Security settings
- Security awareness training assigned to all staff
- Completion tracked and chased
- Training records retained as evidence
OneClickComply Companion
- Opened Faithlife with your existing session
- Reading users, course assignments, completion records
- Security awareness training assigned to all staff
- Completion tracked and chasedGap found, fix it in one click with OneClickFix
- Training records retained as evidence
Evidence saved and mapped
Faithlife evidence, collected automatically
The Faithlife evidence auditors ask for, captured on a schedule and stored against the right requirement. No more screenshots the week before the audit.
- Users
- Course assignments
- Completion records
- Admin roles
Mapped to your frameworks
Every Faithlife check is mapped to the controls it satisfies, so one piece of evidence counts everywhere it applies.
Set up in minutes
How to connect Faithlife to OneClickComply
- 1
Add the browser extension
Install the OneClickComply Companion, our AI browser agent. There's no API key to create and nothing to change in your stack.
- 2
Open Faithlife as normal
The Companion reads Faithlife's admin settings that matter for compliance, using the access you already have. No extra logins.
- 3
Fix it in one click
Settings are checked against your controls and the evidence is stored. When something fails, OneClickFix can correct it in Faithlife for you, with the change logged as evidence.
See Faithlife checked live against your controls.
Faithlife security & compliance FAQs
How does OneClickComply connect to Faithlife?
Through the OneClickComply Companion, our AI browser agent. It reads Faithlife's admin settings using the access you already have, so there's no API key to create and no extra login. When a setting fails a check, OneClickFix can correct it for you.
What does OneClickComply check in Faithlife?
Its checks for Faithlife include: security awareness training assigned to all staff, completion tracked and chased and training records retained as evidence. Each result is stored as evidence against the requirement it satisfies.
What Faithlife evidence do auditors ask for?
For learning and training tools, auditors usually want users, course assignments, completion records and admin roles. OneClickComply captures it on a schedule, so it's ready before they ask.
Which frameworks does the Faithlife integration cover?
Faithlife evidence is mapped to SOC 2, ISO 27001, Cyber Essentials and NIST CSF.
Also connects with
Other learning and training tools we connect to
Using more than one learning and training tool? OneClickComply connects to these too, so your evidence stays in one place.
Get Faithlife audit-ready this week
OneClickComply connects to Faithlife and the rest of your stack, collects the evidence and tells you exactly what to fix. If it has a web admin console, we can work with it.
Logos provided by Logo.dev. All product names and logos are trademarks of their respective owners.