Edit a band set with your team

What is multiplayer editing?

Multiple people on your team can edit the same band set at the same time. Instead of copying a band set for each person and merging the results by hand, your whole team works in one band set, split by region, job family, track, or however you divide the work.

To keep edits from colliding, Pave locks whatever you're working on. While you're editing a band, other people can see it but can't change it. You can see who's working on what, and everyone sees your changes as soon as you save.

• Work in parallel: each person edits their own bands, grades, or benchmarks without waiting for others to finish.
• See who's editing what: locked rows show the name and avatar of the person editing them.
• Stay in sync: saved changes appear for everyone in the band set automatically, without a page refresh.
• Know before you disrupt someone: Pave warns you before actions that affect a teammate's work, and lets them know when their work changes.

To edit a band set, your role needs the Band admin permission.

How locking works

Pave locks the specific item you're working on, not the whole band set. Each area locks a little differently.

Area	What gets locked	When the lock starts	When the lock ends
Bands and benchmarks	The row you're working on	When you select the row or start editing a cell	When you deselect the row, or when you save or cancel if you've made edits
Grades	The whole grade band, including every job in it	When you start editing the grade	When you save or cancel your edits
Band sidepeek	The band and its benchmarks	When you open the band's sidepeek	When you close the sidepeek, or when you save or cancel if you've made edits
Benchmark sidepeek	The whole ladder	When you open the benchmark sidepeek	When you close the sidepeek, or when you save or cancel if you've made edits
Data rules	The data rule	When you open the data rule	When you close the data rule
Mappings	All mappings in the band set	When you select Edit on the Mappings page	When you save or cancel, or leave the Mappings page

Row locks are shared between the Bands and Benchmarking tabs, across all pay types. If a teammate is editing a band on the Bands tab, you can't edit that band's benchmarks on the Benchmarking tab until they're done.

See who's editing

When someone else is editing an item, Pave shows you who it is:

• Rows: the row's checkbox is replaced by the editor's avatar. Hover over it to see "[Name] is currently editing this row." If they're editing a whole ladder or grade, the avatar appears on the group's header.
• Sidepeeks: a View only label appears in the header, with a note saying who's editing. You can read everything, but editing options are hidden or turned off.
• Data rules: a note says who's editing the rule. The rule is read-only, and you can only close it.
• Mappings: the editor's avatar appears in the page header, and Edit and Upload CSV are unavailable until they're done.

If you try to select rows someone else is editing, Pave tells you how many rows couldn't be selected. The rest of your selection still works.

Save your work and see others' changes

Edits you make in the Bands or Grades grid stay private until you select Save. Teammates see your changes after you save, and you see theirs after they save. The grid updates on its own, so there's no need to refresh the page.

Changes you make in a benchmark sidepeek, such as adding a manual benchmark or adjusting weighting, don't have a separate save step. They apply for everyone as soon as you make them.

Save or cancel when you're done with a set of rows. This releases your locks so teammates can edit those rows. While you have unsaved changes in a row, that row stays selected and locked to you.

If you try to leave a band set with unsaved edits, Pave asks whether to Discard changes or Keep editing.

Actions that affect others' work

Some actions affect teammates working in the same band set. Pave warns you before you take them, and lets affected teammates know when their work changes.

Band set actions

Before you take these actions, Pave shows who's currently editing so you can check with them first. You can still go ahead.

• Publish, archive, or delete: Pave lets you know there are edits in progress so you can ask them to save first. If a band set is archived or deleted, edits that weren't saved can't be saved afterward.
• Download: Pave explains that the download won't include changes people haven't saved yet. You can select Download anyway or wait until they save.
• Upload: uploading a band CSV or job-to-grade associations while anyone else is in the band set shows a warning first.

If someone publishes, archives, or deletes a band set while you're in it, Pave tells you who did it. For an archived or deleted band set, you can select View all band sets to return to your list.

Data rules, regeneration, and benchmark edits

Some changes update data a teammate is actively editing. Pave asks you to confirm before the change applies, and lets the affected teammate know what's changing.

• Data rules: editing a data rule that updates benchmarks someone else is editing. The teammate is notified that their benchmarks are changing.
• Mapping regeneration: regenerating a job mapping while someone has benchmark edits in progress for affected jobs. The teammate is notified that mappings are changing.
• Auto-smoothing, pay zone differentials, and midpoint or level progression: running any of these while someone is editing the data it depends on.

Divide work with saved views

Multiplayer lets several people edit one band set, and saved views help each person focus on their part of it. Pair the two to give each team member their own slice of the band set without setting up formal permissions or assignments.

For example, if your team splits a repricing by job family:

1. Each person filters the Bands or Benchmarking tab to the job families, pay zones, or tracks they own.
2. They save that setup as a personal view, such as "Engineering and Product."
3. Each time they open the band set, they apply their view and see only their bands.

Band admins can also create a company view for each workstream, such as "EMEA" or "Sales roles," so every person on that workstream starts from the same setup.

Because each person works in a different set of bands, they rarely run into each other's locks. Keep in mind that views control what each person sees, not what they're allowed to edit. Anyone with the Band admin permission can still open and edit any band in the band set. For details on creating views, see the article on saved views.

Things to know

• Unused locks expire after 24 hours. If someone leaves an edit open for 24 hours without activity, Pave releases it and discards their unsaved edits.
• Some deletes wait until edits are done. You can't delete a band someone else is editing, or delete a job while the band set has open edits. Save or discard edits first.
• The audit log shows who changed what. Each saved change is recorded in the band set audit log under the name of the person who saved it.
• If your connection drops, Pave shows a message that your data might be out of sync, and another when the connection is restored and your data is up to date and can be edited again.

Frequently asked questions

What happens if a teammate archives or deletes the band set while I'm editing? You can't save your remaining edits. Before archiving or deleting, your teammate sees a warning listing you as someone currently editing, and afterward Pave tells you who archived or deleted the band set.

Will my teammate see my changes while I'm typing? No. Teammates see your changes only after you select Save.