Every grade that shows up in a family portal, every completion record that lands in an HR system, and every roster that populates on day one of class started as a setting in Canvas. When those settings are right, data moves quietly in the background and nobody notices. When they're wrong, a teacher loses a Friday re-entering 40 scores by hand, a registrar can't certify enrollment, or a compliance officer can't prove an employee finished required training on time.
A misconfigured sync rarely throws an alarm. It shows up weeks later as a missing grade, a duplicate enrollment, or a compliance report nobody trusts, and by then it's hard to trace back to the setting that caused it.
This is the second post in our series on Canvas configuration and governance. Post one covered access, ownership, and academic integrity. This post covers the settings that connect Canvas to the systems your institution actually runs on: your student information system (SIS), your CRM/HRIS/CSV upload, and the exports your team pulls for backup, audit, or reporting.
Where Sync Starts: CSV upload and SIS/CRM/HRIS Integration
Most data problems in Canvas don't start in Canvas. They start with a mismatch between Canvas and the system of record sitting next to it. SIS Imports handle the bulk creation of users, courses, and enrollments through a CSV file or a direct API connection, and confirming this is enabled and running on a predictable schedule is the foundation everything else in this post depends on. If your SIS import job is stale, silently failing, or running on a schedule nobody remembers setting, every downstream setting we cover here is working with bad information.
For business and government accounts, CRM/HRIS/CSV integrations carry the same weight for a different reason. When an employee joins, changes roles, or leaves, their Canvas access and training records need to update on their own. Manual provisioning creates two predictable failure modes: new hires who can't reach onboarding content on their first day, and former employees who keep an active account long after they've left. Automating enrollment and deactivation closes both gaps, and it gives you a compliance audit trail that doesn't depend on someone remembering to update a spreadsheet.
Suggested resource:
What are SIS Imports?
Grade Passback Defaults
Grade passback, sometimes shortened to GPB, is the process that sends scores from the Canvas gradebook back to your SIS. Two account settings decide how much of that process is automatic and how much depends on an instructor remembering to check a box.
The first is whether new assignments, quizzes, and graded discussions sync to your SIS by default. Leaving this off means every instructor has to opt in item by item, and any instructor who forgets simply doesn't send that grade anywhere. The second is whether Canvas automatically stops posting to SIS once a grading period closes. Without this, a grade change made after the fact can quietly overwrite an official record that was already finalized in your SIS. Reviewing both settings, and pairing them with the nightly automatic sync option instructors can turn on, closes the gap between what a teacher enters and what actually reaches the system your registrar or HR team relies on.
Suggested resource:
How do I set up automatic grade sync from Canvas to my SIS gradebook?
Grading Categories
Everything above assumes the sync has somewhere to land, and that's not guaranteed. Most SIS-managed grade passback runs on a bridge between Canvas assignment groups and grading categories defined in the SIS, and that bridge is a different kind of problem than the rest of this post. It isn't an account setting. There's no checkbox on the account settings page that governs it. It lives in how each course is built, which means it's easy to overlook precisely because nobody thinks of it as a setting at all.
When an assignment group in Canvas doesn't line up with a category the SIS recognizes, one of two things happens. Either the sync rejects the grades tied to that group, or it accepts them into the wrong category. A wrong category is often harder to catch than an outright failure, since the grade did technically arrive somewhere. This is one of the most common root causes we see behind "grades didn't pass back" tickets, and it's rarely obvious from inside Canvas that it's the cause.
Because this lives at the course level rather than the account level, the fix is a governance one more than a settings one. Standardizing assignment group names and weights in your course templates or blueprint courses, so every section that copies from them inherits the same structure your SIS expects, keeps individual instructors from having to get this right on their own. If your institution doesn't build courses from a shared template, this is worth documenting clearly anyway, since it's one of the few items in this post that a single admin can't fix with a setting change alone.
Suggested resource:
How do I sync my Canvas assignment groups with SIS grading categories for grade passback?
Due Date Requirements
Most SIS grade passback integrations, including Skyward, Infinite Campus, PowerSchool, and ProgressBook, will only accept an assignment that has a due date, and that date has to apply to the whole section rather than to individual students. An assignment without one doesn't sync, and it usually fails without much of a visible error, so the first sign of trouble is a missing column in the SIS gradebook weeks later.
Requiring a due date on every graded item at the account level closes this gap before it starts. It also has a side benefit for the learner experience: due dates drive the to-do list, calendar, and late policies that keep students oriented in a course, which we'll get into more in a future post in this series.
Suggested resource:
What is the difference between assignment due dates and availability dates?
Assignment Name Limits
This one catches even experienced admins off guard. Many SIS platforms cap the assignment name field at 255 characters, and Canvas doesn't stop an instructor from naming an assignment something longer. The result is a sync that either truncates the name into something unrecognizable in the SIS gradebook or fails outright, and both outcomes are hard to trace back to their cause without knowing to look for it.
There's no account setting that raises that limit, since it lives in your SIS rather than in Canvas. What you can control is whether instructors know about it. Put the character limit in your onboarding materials and grading documentation, and pair it with the SIS friendly name field, which lets you rename the sync checkbox instructors see so it matches your actual platform instead of a generic label that doesn't mean anything to the person clicking it. That won't stop a long assignment name from being typed in the first place, but it puts the limit in front of the people who need to know it.
Suggested resource:
How do I set details for an account?
Gradebook Exports
The Gradebook CSV export is one of the most-used features in Canvas, and one of the most misunderstood. It's a snapshot, not a sync. Exporting the gradebook to reconcile grades, back up a course before an SIS migration, or hand a report to an academic dean is exactly what it's built for. Treating it as an ongoing substitute for SIS integration is where things go wrong, since nothing about the export updates automatically and nothing you edit in that spreadsheet writes back to Canvas unless you re-import it.
A few details matter when you do rely on an export. Some columns, including current score and final score, are calculated by Canvas and get ignored if you edit them and re-upload the file. A grading period filter narrows the export to that period, but assignment group totals still reflect the whole course. And an export doesn't capture everything a full course export does: it's grades only, not the pages, files, and modules that make up the course itself. Knowing which export solves which problem keeps your team from reaching for the wrong tool during an audit or a migration.
Suggested resource:
How do I export grades in the Gradebook?
A Word on Access
None of this works if the wrong people can edit it. Limiting who can rename courses, change SIS sync settings, or modify due dates after a grading period closes protects the integrity of everything above, and we covered the permission and access settings that support this in post one. Access controls decide who can touch a setting; the settings we covered here decide what happens once they do.
Final Thoughts
Data integrity in Canvas isn't one setting. It's a chain: SIS and HRIS integration bring people and courses in, grade passback settings decide what syncs and when, due date requirements [and grading category association] decide whether that sync succeeds,, and gradebook exports give you a way to check the work. A gap anywhere in that chain shows up somewhere else, usually far from where it started.
If it's been a while since anyone reviewed this part of your account, or if you've had turnover on your admin team, our Canvas Continuity Check service walks through your settings and your data workflows with one of our specialists. Reach out to your Customer Success team to get started.
