Structures: drafts, publishing and conflicts

A map is a draft until you press Publish to the organization (this replaces Update and sync to system where the new tools are on). The preview lists every change and checks it first:

• No reporting loops, and one solid-line manager per box.
• Units only under a higher level, and sub-teams one level deep.
• Renames made on the map go through the normal rename doors. The preview names any rename you cannot make (team renames need manage members), and the result lists any rename that was not made.
• A unit renamed both in Settings and on the map must be resolved: keep the map's name or use Settings'.
• A unit deleted in Settings asks you to unlink or remove the box.
• A linked team drawn under another linked division or department (or under a department this publish creates) is moved there when you publish. The preview says so under Publishing also changes where units sit. Moving needs manage members; a move you cannot make is shown and not made. Teams are never moved into or out of a sub-team, and groups are never moved.

A publish that only renames or moves

When a map's only changes are renames, new departments or moved teams, publishing takes its own press: Publish renames (or Publish these changes). The people who manage members are sent a notice, and the result says how many were told.

Every publish is one entry in the map's History ("Published to the organization").