Confluence already turns many pasted URLs into Smart Links, can suggest related content under documented conditions, and provides quick and advanced search. A deliberate manual block may cover the remaining high-value links.
Choose native links and discovery when readers can find and understand the required context. Choose a manual block when a page owner must curate a small authoritative set.
Context Linker is a concept panel with no remote index, search implementation, distributed version, Marketplace listing, installation test, verified permission filtering, price, or support commitment.
Test discoverability with the same pages, permissions, queries, and reader tasks. Do not treat more suggested links as a better outcome.
Official Confluence documentation covers Smart Link display, automatically generated related-content suggestions, and quick or advanced search with context and filters. Each mechanism has distinct prerequisites and permission behavior.
A page owner can maintain a short, typed list of decisions, Jira work, source documents, and why each relationship matters.
The hypothesis is a context panel that suggests typed relationships and requires confirmation before adding them. It must prove permission-safe retrieval and useful reasons, not link volume.
Blocked: concept only, no search index or permission test
Native display, native discovery, manual curation, and assisted suggestions solve different problems. The smallest reliable mechanism should win.
| Criterion | Native baseline | Manual baseline | Concept hypothesis | Decision rule |
|---|---|---|---|---|
| Known references | Pasted URLs can become Smart Links with supported display choices; access to source content still matters. | Owner adds a small set of explicit links and relationship descriptions. | Would type and display confirmed relationships in a dedicated panel. | Keep Smart Links or manual links when the references are already known. |
| Passive discovery | Related content can suggest accessible pages after its documented content, readership, and space-setting requirements are met. | Owner chooses related items based on the page's intended journey. | Would need to explain every suggestion and allow confirmation before creating a relationship. | Keep related content when its suggestions solve the reading task. |
| Active retrieval | Quick and advanced search cover content types, highlighted terms, breadcrumbs, dates, spaces, contributors, and other filters. | Curated links remove search effort for a narrow repeated task. | Would need a measured contextual-retrieval improvement without hiding native search. | Reject the concept when a saved query or clear page structure is sufficient. |
| Permission and governance | Related content only shows suggestions the viewer can access; external Smart Links can require source authentication. | Owner must periodically verify access and relevance. | Would add cross-product scopes, indexing rules, retention, permission filtering, support, and deletion obligations. | Stop until zero unauthorized title, excerpt, or relationship leakage is demonstrated. |
Context is useful only when it is relevant, explainable, current, and authorized.
Not every URL can be fully displayed, and readers may need authentication and source-app access.
Suggestions require substantive content and readership, respect access, and can be disabled by a space administrator.
No current index, relevance test, permission test, or production data flow supports the suggested-link demonstration.
Claims about Confluence discovery and permissions are limited to Atlassian Support documentation. Re-test them with representative content and access roles.
Reviewed
Official Atlassian source
Smart Link creation and views, Jira and third-party links, authentication, and Rovo summaries.
Open sourceOfficial Atlassian source
Suggestion behavior, reason display, content and readership prerequisites, permissions, and space-admin control.
Open sourceOfficial Atlassian source
Quick and advanced search, content types, result context, dates, breadcrumbs, and filters.
Open sourceUse representative access roles and treat any permission leak as a hard stop.
Explore the intended context panel with fictional relationships and explicit confirmation.
Open demoInspect intended indexing, confirmation, permissions, checks, and limits.
Open documentationReview the blocked compatibility, data, verification, and support evidence.
Open trust profileEnter your retrieval volume, effort, costs, and realistic adoption.
Open ROI modelRecord roles, queries, expected links, forbidden results, sources, and stop conditions.
Open evaluation roomContinue only when a measured contextual-retrieval gap remains and a real implementation proves relevance, explanations, permission fidelity, deletion, and safe failure.