Administrator

Clever is a rostering and single sign-on platform many school districts use to connect their student information system (SIS) with the applications they use, including Buzz. For these FAQs, Buzz is the LMS receiving the data.

Yes. Clever sync must be enabled for your domain before you can connect. If you're interested in setting up Clever sync, or have questions about whether it's available for your domain, reach out to your account manager.

Clever rostering is API only. There's no file to upload — Buzz connects directly to Clever's API and pulls (reads) your roster data.

Buzz uses Clever API v3.1.

No. The Clever SIS Sync does not support grade passback; grades stay in Buzz.

No. A domain can be configured for OneRoster or Clever, but not both at the same time.

To use the SIS Sync, the Buzz administrator must have each of the following domain privileges. Missing any of them won't cause an error — the SIS sync menu item simply won't appear for that administrator.

• Domain
  • Owner
  • Create
  • Read
  • Edit
  • Delete
  • Report
• Users
  • Owner
  • Create
  • Read
  • Edit
  • Delete
  • Report
• Courses
  • Owner
  • Create
  • Read
  • Read full
  • Edit
  • Delete
  • Report
• Enrollments
  • Owner
  • Read
• Grades
  • Grade assignment
  • Grade discussion
  • Grade exam
  • Setup gradebook
  • Read gradebook
  • Submit final grade

The SIS Sync may create, update, and delete the following entities shared with Buzz:

• Users: students, teachers, district administrators, and school staff
• Courses: a section course per Clever section, plus optional district, school, and teacher base courses
• Enrollments: student and teacher enrollments (a section with more than one teacher gets one enrollment per teacher)
• Administrator/staff access: granted at the district and/or school level, based on the roles you've configured

Domains work a bit differently: the sync creates one new domain per Clever school and renames it if Clever renames the school, but it never deletes a domain. When a school stops being shared, its users, courses, and enrollments follow whatever un-shared settings you've configured — the domain itself stays.

"Their school" means the student or teacher's primary Clever school. If that school isn't shared but another of their schools is, their account is placed there instead of being left out entirely.

If a person holds more than one Clever role, they still get exactly one Buzz account — a teaching role always wins. A district administrator who also teaches, for example, gets a teacher account in their school domain, with their administrator access attached to that account.

Yes. Clever allows more than one teacher to be listed on a section, and the SIS Sync handles this correctly — each teacher gets their own teacher enrollment on the section course.

One nuance for teacher base courses: only the primary teacher on a section gets their own teacher base course. Any additional (co-)teachers are enrolled in the primary teacher's base course rather than getting one of their own.

Yes. Single sign-on works in both directions: a user can click into Buzz from their Clever Portal, or start at Buzz and be sent to Clever to sign in. Accounts the sync creates are SSO-only — they don't have a separate Buzz password. SSO is configured by Agilix.

Buzz allows for derivative courses to be managed (e.g., settings, content) from a base course. The derivative course receives updates from the base course as long as it wasn't explicitly changed in the derivative course. This allows for efficient curriculum development and distribution while still letting teachers and schools further enhance their own course.

For Clever, the SIS Sync can optionally create up to three layers of base course, grouped by course number: one at the district level, one at the school level, and one at the teacher level. Each layer derives from the one above it, and the section course derives from whichever layer is enabled and closest to it (teacher, then school, then district).

All three layers are off by default, and can be turned on independently when you configure the sync. Once a base course has been created by a sync, it can't be automatically removed by the sync, even if you later turn off that layer's checkbox. If base courses haven't been added by the sync, you can choose to add them using the sync later.

Turning a layer off doesn't leave existing section courses pointed where they were, though: on the next sync, their section courses are re-pointed to derive from the next layer up instead. Turning a layer back on later reverses this, re-pointing section courses back down to it.

A base course is created for each unique course number found in your Clever data, at whichever layer(s) you've enabled. All three layers are keyed on course number, so if your Clever data doesn't include course numbers, no base courses will be created at any layer, regardless of which checkboxes are enabled.

• District base course: Nobody automatically. Buzz Administrators should manually enroll curriculum developers and other users, as necessary.
• School base course: Nobody automatically, unless you've turned on the option to enroll a section's teachers in the school base course.
• Teacher base course: The primary teacher of the course. Co-teachers on the same section are enrolled in the primary teacher's base course instead of getting their own.
• Section course: The teacher(s) and students of that section.

Yes. Clever has native district administrator and staff role types, and the SIS Sync creates those accounts and grants them administrator access according to the roles you've configured for your domain.

Generally, no — if you manually change a field that's managed by the sync (like a student's name), it will likely be reverted the next time the sync runs. Any changes should be made in Clever instead.

Administrator and staff access is handled a bit more carefully: access you grant to someone by hand, outside of what the sync manages, is never touched or removed by the sync.

External IDs generated in the sync in Buzz include "Clever."

• Course external IDs include clever-co
• Student enrollment external IDs include clever-se
• Teacher enrollment external IDs include clever-te
• District base course external IDs include clever-dm
• School base course external IDs include clever-sm
• Teacher base course external IDs include clever-tm

You can trigger a sync on demand at any time from the SIS sync screen in Buzz. If you'd like it to run automatically on a schedule — once or twice a day is typical for a nightly SIS feed — reach out to Agilix Support to have it scheduled.

Students and teachers are created in the domain for their school. District administrators and staff are created in the District domain itself.

District base courses are created in the District domain. School base courses and teacher base courses are created in the relevant school domain. Section courses are created in the domain for the school that section belongs to.

You control this yourself when you configure the sync:

• Un-shared users: Do nothing, Mark as inactive, or Delete.
• Un-shared courses: Delete or Do nothing.
• Un-shared enrollments: Do nothing, Mark as inactive, Mark as withdrawn, or Delete.

Removal only ever applies within the current term — a course or enrollment from a term that has already ended is never a deletion candidate, so a pull that's missing an entire term can't wipe out that term's history or grades.

If something is deleted and then shared again later, Buzz restores the original record — including its history — rather than creating a duplicate, as long as the add setting is left at its default.

A domain that already carries an external ID — for example, one already configured for another sync — can't be used for a Clever sync at all; the sync will refuse to run. Beyond that, because the Clever SIS Sync always creates brand-new school domains rather than matching into ones you already have, we recommend using a brand-new, empty District domain for the sync. Any users or courses already in a domain you reuse for the sync (that doesn't already have an external ID) simply won't be picked up by it — they'll sit alongside the synced data rather than being included in it.

If a user moves between two schools that are both part of the same sync, the sync moves their account to the new school along with their history, rather than deleting and recreating them — so their identity and past work (like grades) aren't lost in the move.