Trust
Built to be trusted with your week.
Your schedule is what your whole practice runs on. Canopy records every change and lets you take it back, keeps each practice's data to itself, and backs everything up every night.
Nothing changes without a record
Every change is accounted for, and reversible.
History is written by the database itself on every save, so it can't be skipped or forgotten.
Who, what and when
Each session keeps its own history: every edit, move, cancellation and restore, with who made it.
Restore any version
Preview an earlier version of a session and put it back exactly as it was.
Recently deleted
Deleted sessions are kept, so you can bring one back instead of rebuilding it.
Undo skipped sessions
Skipped or removed a generated session? Put it back from the exceptions page.
Regenerating is safe
Rebuilding a week never rewrites a session someone changed by hand, covered or cancelled.
A practice-wide feed
The Recent changes page shows everything that changed across the schedule, newest first.
Everyone on the same page
You know who's seen what.
Acknowledgements
Every schedule change goes to the staff it affects, and the acknowledgements tracker shows who has confirmed it.
One source of truth
The web and every phone read the same live schedule. There's no copy to fall out of date.
Changes come with reasons
Call-outs record why a session was cancelled, so the record makes sense months later.
Your data stays yours
Each practice is walled off from every other.
Access rules live in the database, not just in the app, so they hold no matter what screen someone is on.
Practice-level isolation
Database row-level security means a signed-in person can only ever reach their own practice's rows.
Managers change, staff view
Staff see the schedule read-only and can answer only for their own sessions, through narrowly guarded actions.
Access that ends
When someone leaves, set an end date and their access stops.
Clients by nickname
Clients are kept by nickname or initials. Canopy is built for scheduling, not clinical records.
Encrypted in transit
Every page and app request travels over HTTPS.
Behind the scenes
Backed up, rehearsed and kept running.
Nightly off-site backups
The database is backed up every night to separate storage, away from the servers that run the app.
Write-once storage
Backups are locked when they're written, so they can't be altered or deleted during the retention window.
Restores we actually test
Restoring from a backup is rehearsed, not assumed.
Rehearsed releases
Every update is run against a copy of the live database and an automated test suite before it ships.
No downtime updates
New versions go live alongside the old one and switch over only once they're healthy.
Have a question about how your data is handled? Email us and you'll hear back from the people who built it.
Make a change, then undo it, in the demo.
Questions first? Email us and a real person will write back.