Content connectors
Content connectors
A connector links your organisation to an external content system. Once connected, a blueprint tab can render content from it in place, rather than holding a copy that drifts.
Managing connectors needs integration.manage.
Source-embed tabs
A source embed tab names a page in the connected system. Blueprintr fetches it when the blueprint is read, using the viewer's own permission in the source system.
A source embed resolves per viewer, with that viewer's access. Someone who cannot read the Confluence page cannot read it through Blueprintr either. The content is never cached into a surface with different permissions.
Because it is a per-viewer privileged fetch, source-embed tabs do not render on anonymous surfaces: marketing pages, public embeds, or a frozen version snapshot. Those show an inert reference card instead.
Import versus connect
Importing copies content in once and it becomes yours. A connector leaves the content where it is and renders it live. Import when you are migrating; connect when the other system stays the source of truth.