Personal overlay

Every member has a private overlay on top of the shared Blueprint. Console writes the Blueprint. The organization collection writes only that person's overlay — including when the person is an admin.

What the overlay may change

• Rename a Blueprint folder or bookmark, change its note, icon, or color.
• Reorder tiles and change wallpaper, theme, or start page for that person only.
• Add personal folders and links (origin: personal).
• Pin a Blueprint item under a different parent so a later Blueprint move does not follow.

Overlay objects keep an origin: blueprint for Admin items the member restyled, personal for items they created. Personal folders may sit inside a Blueprint folder.

What the overlay cannot do

• It cannot reveal a Blueprint item the member's roles hide. Filtering happens first.
• It cannot edit the shared Blueprint. That happens only in Console → Blueprint.
• It cannot share a Blueprint folder or bookmark. Only personal items can be shared with other members.
• Search and the consume API never return hidden Blueprint items through the overlay.

When Admin changes the Blueprint

• New Blueprint objects appear under the same stable folder ID for every member, appended at the end — even if that member renamed the folder.
• If Admin deletes a Blueprint folder, personal children move to the next living Blueprint ancestor or the collection root.
• If Admin moves a Blueprint item, members follow unless they pinned their own parent.

Restore

Restore logo, color, title, and description on a Blueprint bookmark. On a folder, the same fields reset for that folder and every Blueprint descendant. Personal children stay. Restoring the collection root also resets wallpaper, theme, and view to Blueprint defaults.

POST /api/org/:slug/restore
{ "scope": "bookmark" | "folder" | "collection", "id": "bm_…" }

PATCH /api/org/:slug/collection
  stores only this member's overlay

Blueprint, restore, and internal sharing are also covered in Blueprint. Visibility rules live in Roles and visibility.