Nobody in K-12 has time to maintain the same list of people in two places. You already keep your staff and students in Google Workspace. You manage them there every day. The last thing you need is a second tool asking you to type all of that in again and then keep it updated by hand forever.
So Edventory syncs from Google instead. It reads the roster you already maintain, maps it in, and keeps it current. Setup that would otherwise be a week of data entry becomes a connection you turn on. The same goes for pulling device information in from your MDM. The systems that already hold the truth get to be the source of truth, and Edventory reflects it.
There is a privacy reason I like this approach too, not just a convenience one. When you sync from the system of record, you are not creating a permanent second copy of sensitive data that lives forever in another vendor's database. You are reflecting what is already managed where it should be managed. Pull what the work needs, keep it current, and do not hoard a stale duplicate. That is a healthier way to handle student and staff data, and it happens to also be the less annoying way.
The principle underneath is the one I keep coming back to. Meet people where they already are. Your roster lives in Google, so Edventory reads it from Google. You should not have to do data entry to use a tool whose whole job is to save you time.