# Context Linker — Machine-readable product concept documentation

> Unpublished interactive concept. This document is not a Marketplace listing, installation guide for an available app, compatibility certification, security attestation, or statement of Atlassian endorsement.

- **Document type:** Machine-readable product concept documentation
- **Document language:** English (en)
- **Product slug:** context-linker
- **Commercial status:** Concept not published on Atlassian Marketplace
- **Latest registry review:** 2026-08-12

## Product overview

- **Product concept:** Context Linker
- **Intended host product:** Confluence
- **Proposed placement:** Context panel
- **Intended audience:** Knowledge, delivery, and governance teams
- **Product intent:** Find related projects and decisions without leaving the page.

The panel gathers peripheral context in a dedicated area so the document stays readable and links remain verifiable.

## Canonical sources and language versions

- **Canonical HTML source:** https://www.addly.app/en/docs/context-linker
- **English Markdown version:** https://www.addly.app/en/docs/context-linker/document.md
- **French Markdown version:** https://www.addly.app/fr/docs/context-linker/document.md
- **Default-language Markdown version:** https://www.addly.app/en/docs/context-linker/document.md
- **Interactive concept demonstration:** https://www.addly.app/en/addons/confluence/context-panel
- **Product trust profile:** https://www.addly.app/en/trust/apps/context-linker
- **Public compatibility register:** https://www.addly.app/en/integrations#compatibility-context-linker

## Before any installation

- Confirm that Confluence Cloud and the Context panel placement match the need.
- Identify the administrator responsible for configuration.
- Review the intended permissions and data flow.
- Choose a test project or space with no sensitive data.
- Define the critical path and expected result.

## Installation status and future sequence

**No installation is available.** The future guide must start from the official Marketplace listing, verify the vendor identity, show the requested permissions, and confirm the target Atlassian site.

- Open the official listing linked from the product page.
- Review hosting, version, permissions, and the data policy.
- Install on an authorized test site.
- Verify that the surface appears in the expected context.

## Illustrative configuration

Configuration should start small and produce an observable result. The following settings are illustrative and must be replaced by the real schema.

```json
{
  "surface": "Context panel",
  "scope": "test-project",
  "mode": "preview",
  "data": "demonstration-only"
}
```

Preview mode should let the result be verified before broad activation.

## Intended permissions

### 1. Read the current page

- **Functional scope:** Page content and metadata the person can already view
- **Rationale:** Base suggestions on the displayed document’s context
- **Evidence state:** Needs confirmation
- **Source URL:** https://www.addly.app/en/trust/apps/context-linker#permissions
- **Last reviewed:** 2026-08-12

### 2. Search authorized spaces

- **Functional scope:** Accessible pages in explicitly included spaces
- **Rationale:** Suggest related documents without exposing private content
- **Evidence state:** Needs confirmation
- **Source URL:** https://www.addly.app/en/trust/apps/context-linker#permissions
- **Last reviewed:** 2026-08-12

### 3. Read selected Jira context

- **Functional scope:** Jira projects and issues already accessible to the person
- **Rationale:** Connect the page to tickets confirmed by the user
- **Evidence state:** Needs confirmation
- **Source URL:** https://www.addly.app/en/trust/apps/context-linker#permissions
- **Last reviewed:** 2026-08-12

### 4. Save a confirmed relationship

- **Functional scope:** An app-owned typed link between two authorized content items
- **Rationale:** Keep the relationship only after explicit confirmation
- **Evidence state:** Needs confirmation
- **Source URL:** https://www.addly.app/en/trust/apps/context-linker#permissions
- **Last reviewed:** 2026-08-12

## Data categories and current state

### 1. Demonstration data

- **Data source:** Fictional dataset embedded in the public showcase
- **Purpose:** Make the scenario interactive without customer data
- **Storage:** Local demonstration-interface state
- **External transfer:** No remote product service connected in this showcase
- **Retention:** No remote product retention in the demonstration
- **Deletion:** Demo reset or session close
- **Processing region:** Viewer’s browser
- **Evidence state:** Available
- **Source URL:** https://www.addly.app/en/addons/confluence/context-panel#demo
- **Last reviewed:** 2026-08-12

### 2. Authorized Confluence and Jira context

- **Data source:** Current page, included spaces, and selected projects — product intent
- **Purpose:** Search for and explain relevant relationships
- **Storage:** Production architecture to be defined
- **External transfer:** To be confirmed with the published architecture and manifest
- **Retention:** To be defined for possible indexes, caches, and results
- **Deletion:** To be defined for removed content and uninstall
- **Processing region:** To be defined before any publication
- **Evidence state:** Needs confirmation
- **Source URL:** https://www.addly.app/en/trust/apps/context-linker#data
- **Last reviewed:** 2026-08-12

### 3. Confirmed relationships

- **Data source:** Links validated by a person — product intent
- **Purpose:** Restore explicit, auditable context
- **Storage:** Planned app storage; architecture not finalized
- **External transfer:** No production recipient defined
- **Retention:** To be defined with the linked-content lifecycle
- **Deletion:** Link deletion and uninstall need specification
- **Processing region:** To be defined before any publication
- **Evidence state:** Needs confirmation
- **Source URL:** https://www.addly.app/en/trust/apps/context-linker#data
- **Last reviewed:** 2026-08-12

## Compatibility record

> This register inventories product intent and missing verification evidence. It does not prove Marketplace availability, Atlassian approval, a Forge manifest, supported scopes, or compatibility with any host release.

- **Evidence state:** Absent before launch
- **Registry schema version:** 1
- **Stable record identifier:** compatibility:context-linker:concept-0.3
- **Record owner:** Product owner to assign before launch
- **Last reviewed:** 2026-08-12
- **Product state:** Concept only — not published or distributed
- **Concept revision:** 0.3
- **Intended host channel:** Confluence · Cloud target only — not a tested compatibility statement · Connected Jira context intended — not tested
- **Host edition or release:** No tested edition or release recorded
- **Proposed surface or module:** Confluence context panel concept with intended Jira context — no published module manifest
- **Distributed app version:** No app version is distributed
- **Distribution channel:** No package, Marketplace listing, or installation channel
- **Latest compatibility verification:** Never — no versioned build exists to test
- **Verification result:** Not tested
- **Technical support status:** Unverified — no supported host or app version range
- **Test environment:** No compatibility test environment recorded
- **Degraded behavior:** Not defined. It must be implemented and tested for each distributed version before launch.

## Quick start and observable checks

- **Suggested duration:** 8 to 12 minutes
- **Expected evaluation outcome:** Filter three fictional relationships, confirm a link, trigger the no-results state, then restore the initial preset.

### Documented initial state

- Three fictional relationships are suggested and PROJ-248 is selected.
- Search is empty and no relationship has been confirmed.
- The panel queries neither Confluence nor Jira and creates no remote relationship.

### Evaluation prerequisites

- An example page whose project, decision, or document context is currently hard to find.
- The expected authorization rule between Confluence spaces and Jira projects.
- The relationship type that must remain explicit to avoid ambiguous links.
- No real identifier to enter: use PROJ-248 or the suggested fictional labels.

### Interactive steps

#### 1. Filter the project relationship

- **Action:** Enter ‘PROJ-248’ in search.
- **Expected observable result:** The local list narrows to the matching project relationship.

#### 2. Confirm the relationship

- **Action:** Select the visible result, then activate ‘Link selection’.
- **Expected observable result:** A confirmation precisely names the relationship added to this demonstration page only.

#### 3. Test the no-results state

- **Action:** Replace the query with a term that is not present.
- **Expected observable result:** An explicit empty state replaces the list and the linking action becomes unavailable.

#### 4. Restore the preset

- **Action:** Use Reset in the panel, then record the need for deletion and permission controls.
- **Expected observable result:** All three choices return, PROJ-248 is selected again, and the previous confirmation disappears.

### Checks and blocked evidence

- Local search and filtering — Interactive in the local demonstration. Interactive across the three fictional labels.
- Confirmation before linking — Interactive in the local demonstration. Interactive; no relationship is added without an explicit action.
- No-results state and reset — Interactive in the local demonstration. Interactive without reloading the page.
- Cross-product permissions, remote deletion, and suggestion quality — Blocked evidence before publication. Not testable in this fixed list; blocked evidence before publication.

### Troubleshooting

#### Why is Link selection unavailable?

The current selection must remain visible in the filtered results. Clear the query or choose a result that is present.

#### Does the relationship persist after reset?

No. Reset removes the local confirmation. No data is stored outside the component.

#### Can I verify permissions on a real page?

No. The demo shows the interaction model; host-permission filtering must be proven with a real implementation and manifest.

## Evidence register

### Interactive demonstration

- **Evidence state:** Available
- **Details:** The surface and guided path can be inspected with explicitly fictional data.
- **Source URL:** https://www.addly.app/en/addons/confluence/context-panel#demo
- **Last reviewed:** 2026-08-12

### Pre-purchase documentation

- **Evidence state:** Available
- **Details:** The public guide describes the concept’s scenario, expected configuration, verification, and limitations.
- **Source URL:** https://www.addly.app/en/docs/context-linker
- **Last reviewed:** 2026-08-12

### Versioned, tested compatibility

- **Evidence state:** Absent before launch
- **Details:** The register is public, but no distributed version, host version, test date, supported range, or degraded procedure exists yet.
- **Source URL:** https://www.addly.app/en/integrations#compatibility-context-linker
- **Last reviewed:** 2026-08-12

### Exact manifest and permissions

- **Evidence state:** Needs confirmation
- **Details:** Expected actions are documented, but no Forge scope identifier is claimed before a manifest is published.
- **Source URL:** https://www.addly.app/en/trust/security#permissions
- **Last reviewed:** 2026-08-12

### Production architecture and data flow

- **Evidence state:** Needs confirmation
- **Details:** The question model is public; storage, egress, retention, deletion, and region still need confirmation for the real product.
- **Source URL:** https://www.addly.app/en/trust/data#flow
- **Last reviewed:** 2026-08-12

### Atlassian Marketplace listing

- **Evidence state:** Absent before launch
- **Details:** No listing URL, price, review, or installation is invented for this concept.
- **Source URL:** https://www.addly.app/en/pricing
- **Last reviewed:** 2026-08-12

### Independent attestation or certification

- **Evidence state:** Absent before launch
- **Details:** No audit, SOC 2 report, ISO 27001 certificate, or Cloud Fortified badge is claimed.
- **Source URL:** https://www.addly.app/en/trust/compliance
- **Last reviewed:** 2026-08-12

## Known limitations

### Host-permission filtering of suggestions is not proven

- **Evidence state:** Evidence required
- **Functional scope:** Local showcase · Confluence context panel · Confluence and Jira links
- **Rationale:** No host tenant or real permission graph is connected to the prototype.
- **Evaluation workaround:** Evaluate explicit confirmation only and require cross-access tests before processing real content.
- **Last reviewed:** 2026-08-12
- **Source URL:** https://www.addly.app/en/known-issues#limit-context-permissions

The displayed relationships are fictional; the demo cannot verify that a suggestion remains hidden without Confluence or Jira access.

### No remote index or production search is active

- **Evidence state:** Declared limitation
- **Functional scope:** Demonstration · relationship suggestion, typing, and confirmation
- **Rationale:** Search architecture, data, and governance are not yet defined.
- **Evaluation workaround:** Test confirmation with manually entered links and retain the source of each relationship.
- **Last reviewed:** 2026-08-12
- **Source URL:** https://www.addly.app/en/known-issues#limit-context-index

Panel suggestions are demonstration relationships and measure neither relevance, coverage, nor freshness of an index.

- This profile describes a concept and its public showcase, not a published app or security attestation.
- Permissions are functional intentions; they never replace the Forge manifest that is actually distributed.
- Every production architecture, region, retention, deletion, or subprocessor must be confirmed before launch.

## Product questions

### Can the panel expose private pages?

A real implementation must filter every search using the signed-in person’s Confluence and Jira permissions.

### Are links created automatically?

Suggestions may be assisted, but the prototype requires explicit confirmation before a relationship is created.

### Can suggestions be disabled?

The intended configuration separates manual search, suggestions, and space rules so administrators keep control.

## Citation guidance

This Markdown is generated from the same typed registries as the HTML documentation. Preserve every concept, demonstration, draft, blocked, and unverified qualifier when citing it.

- **Canonical HTML source:** https://www.addly.app/en/docs/context-linker