Admin, Manager, or Team Lead role, depending on the task
- Turn outdated change warnings on or off
- Admin role
- Resolve outdated changes
-
Admin, Manager, or Team Lead role
Or a custom role with Edit schedules set to Can edit all agents' schedules or Can edit schedules with custom permissions
Admins set roles and permissions in Manage team > Roles and permissions.
Use outdated change warnings to stop one person’s schedule edits from silently overwriting another’s. Several people can edit the Staffing timeline at the same time. With Prevent saving outdated changes turned on, Assembled checks for edits others have saved to the same agent on the same day, and flags them for you to review before your changes are saved.
To turn it on, go to Configure > Additional settings.
How outdated change warnings work
When you select Save, Assembled checks whether anyone else saved changes to the same agents and days since you loaded the schedule. If they did, your changes aren’t saved. Instead, Schedule updated, changes not saved opens, the schedule updates to the latest version, and each of your changes that’s affected is flagged as one of these:
| Kind | Icon | What it means |
|---|---|---|
| Overridden | Red octagon with an exclamation mark | Someone else changed the same event and saved first. Their change is kept, and yours is removed. |
| Outdated | Orange triangle with an exclamation mark | Someone else changed the same agent on the same day, but not the same events. Both changes are valid; you’re warned so you can check them together. |
| In conflict | None; the events overlap on the schedule | Your change and someone else’s now overlap. Both are kept, and you choose which to keep. |
The first person to save always has their changes saved.
Keep in mind: The warnings don’t force you to fix anything. If you select Save again without making changes, your remaining changes are saved, including any events that still overlap.
Turn on outdated change warnings
This turns the warnings on for everyone in your company.
- Go to Configure > Additional settings.
- In the Staffing timeline card, set Prevent saving outdated changes to Yes.
The setting saves as soon as you change it. To turn the warnings off, set it to No.
Resolve outdated changes
Your unsaved new events are highlighted in orange, so you can tell them apart from saved events.
If others have changed the same agents and days since you loaded the schedule, selecting Save opens Schedule updated, changes not saved:
-
Select Save. If Schedule updated, changes not saved opens, continue with the next step.
-
Select Filter by outdated changes to show only the agents with flagged changes. If you close the dialog instead, the flags stay on the schedule, but the view isn’t filtered.
-
To switch between flagged changes, use Edits view in the filter bar and choose All, Outdated changes, or Overridden changes.
-
To find the days affected, select the warning icon in the filter bar or next to an agent’s name. Days with outdated changes lists them; select a date to go to that day.
-
Review each flagged change, and redo or adjust any of your changes that you still need. To find overlapping events, change All rows to Rows with event conflicts.
-
Select Save again.
Examples
Overridden change
User A moves an event from 9:00 AM–5:00 PM to 10:00 AM–6:00 PM and saves. User B moves the same event to 8:00 AM–4:00 PM and selects Save. User B sees the warning, and their change is flagged with a red octagon. The schedule shows User A’s change. User B can make further changes, or leave the schedule as it is to keep User A’s change.
Outdated change
User A adds an event from 9:00 AM to 10:00 AM to an agent’s schedule and saves. User B adds an event from 12:00 PM to 1:00 PM to the same agent’s schedule on the same day and selects Save. User B sees the warning, and filtering shows that User A added an event. There’s nothing to resolve, so User B can select Save again.
Time conflict
User A adds an Email event from 8:00 AM to 5:00 PM to an agent’s schedule and saves. User B adds a Technical event from 10:00 AM to 2:00 PM on the same day and selects Save. User B sees the warning, and filtering shows the two events overlapping. User B selects one of the events and chooses which to keep, then saves.