Documentation

Console

Blueprint

One Blueprint collection is shared by the whole organization. Members see only what their roles allow, then apply a personal overlay on top. Console writes the Blueprint. The live organization URL writes only that member's overlay. Overlay rules are also in Personal overlay.

Blueprint

Open Console → Blueprint (/console/organization). Wallpaper, theme, start page, folders, bookmarks, positions, icons, notes, and role visibility live here. Only this surface writes TeamspaceCollection.platform.

  • Wallpaper fills the page behind the collection.
  • Theme — System, Light, or Dark, applied to the collection itself.
  • View — Grid (66px tiles, 4 columns on phone, 5 on desktop) or List.
  • Icon radius — corner radius for tiles, same token as Bookmer.

A folder or bookmark with no role assignment is visible to every active member. Admin sees the full Blueprint. New Blueprint objects appear under the same stable folder ID for every member, appended at the end of that folder — even if the member renamed the folder. Assigned SSO applications are merged into this view automatically as tiles (sso_…). They are not stored on the Blueprint.

Personal overlay

Members open /org/:slug. They can rename items, change notes and icons, reorder tiles, change wallpaper and start page, and add their own folders and links. Those edits belong to that person. Admins personalize their own view here too; they change the shared Blueprint only in Console.

Overlay objects keep an origin: blueprint for Admin items,personal for items the member created. Personal items may sit inside a Blueprint 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 from Blueprint

On a Blueprint bookmark, restore logo, color, title, and description. 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_…" }

Sharing

Organizations have no public pages. Members share only folders or links they created (origin=personal) with other organization members. Blueprint folders, Blueprint links, and the collection root cannot be shared.

GET    /api/org/:slug/shares
POST   /api/org/:slug/shares
DELETE /api/org/:slug/shares/:shareId
GET    /api/org/:slug/members

Owner API

GET    /api/developer/teamspaces/:id/collection
PATCH  /api/developer/teamspaces/:id/collection
POST   /api/developer/teamspaces/:id/collection/wallpaper
POST   /api/developer/teamspaces/:id/items
PATCH  /api/developer/teamspaces/:id/items/:itemId
DELETE /api/developer/teamspaces/:id/items/:itemId
POST   /api/developer/teamspaces/:id/items/reorder
POST   /api/developer/teamspaces/:id/items/:itemId/icon
PUT    /api/developer/teamspaces/:id/collection/object-permissions/:objectId

Items are FOLDER or BOOKMARK. Legacy items can usepermissionNodeId; Blueprint objects support multiple assigned roles and use any-match visibility. The object-permissions endpoint accepts { nodeIds: string[] }; an empty array restores organization-wide visibility.