When you edit a setting on one school in a multi-school district, JumpRope can apply the same change to your other schools in one click. This is bulk setup -- a way to keep peer schools in lockstep without re-doing the work N times.

You'll see a bulk-apply prompt automatically when you save a real change to a mastery scheme, an assessment type, a family-portal setting, or when you create a brand-new mastery scheme or assessment type. The prompt only appears if there's a change worth propagating; saving a setting unchanged won't pop the modal.

Who sees the prompt

District-level admins editing on a multi-school district. School-level admins keep the existing per-school edit flow -- bulk-apply doesn't change anything for them.

How "matching" works

The modal splits the schools in your district into three buckets:

  • THIS SCHOOL -- the one you're editing, already saved. Always in the apply set.
  • ALSO APPLY TO -- peer schools whose current setting matches the source's pre-edit value. These are eligible; you opt them in.
  • Not eligible -- peer schools that have intentionally diverged. They don't appear in the modal.

The pre-edit state is what makes this safe to use repeatedly. If you've intentionally given one school a different default weight or a different mastery scheme structure, that school stays diverged. Bulk-apply only follows peers that were already in lockstep with the source -- it never silently steamrolls a school that someone has deliberately customized.

Pick all peers, some, or none

Select all peers, opt in a subset, or apply to just THIS SCHOOL. The footer button tells you exactly how many schools the next click will change.

What happens on the next edit

Say you change a default weight at School 1 and apply it to Schools 2 and 3, but not 4 and 5. Schools 2 and 3 stay in sync with School 1; Schools 4 and 5 keep their old value. The next time you edit the same field at School 1, only Schools 2 and 3 show up in the modal -- Schools 4 and 5 have diverged, so they're now in the "not eligible" bucket until you bring them back in line manually.

What if something fails

If JumpRope can't apply the change to a peer (revoked permissions, a backend hiccup, etc.), the partial result surfaces as an alert listing each affected school and the specific reason. Your source-school change is still saved -- only the peer propagation needs a retry.

Renaming and label changes

You can also rename a peer-able item (e.g. an assessment type from Quiz to Quiz2). Peer-matching uses the pre-edit name, so eligible peers still show up; opting them in renames them alongside the source.

A practical rule of thumb

Treat bulk-apply as a way to propagate intent. Schools that should move forward together stay matched; schools that are intentionally different stay different. The modal makes both states obvious and reversible.