Configure and verify Context Linker.

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

Audience

Knowledge, delivery, and governance teams

State

Interactive concept, not published

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

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

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

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

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

Intended permissions

• 01Read the current page
• 02Search authorized spaces
• 03Read Jira only for accessible projects

Data state

• 01Demonstration relationships
• 02No remote index is active
• 03Host permissions still require validation

Interact with the critical path without leaving the documentation. First observe the initial state, trigger the primary action, then verify that the feedback explains what changed.

Checks to record

• 01The surface appears in the simulated product and context.
• 02Use only exposed controls and record every observable state change.
• 03Verify that the primary action produces the visible feedback described in the demo.
• 04Empty, insufficient-permission, and recoverable-error states cannot be manipulated here: record them as blocked evidence required before publication.
• 05Deactivation and uninstallation cannot be manipulated here: treat them as documentary controls that still need confirmation.

• 01Host edition or release: No tested edition or release recorded
• 02Distributed app version: No app version is distributed
• 03Latest compatibility verification: Never — no versioned build exists to test
• 04Technical support status: Unverified — no supported host or app version range

Any item marked ‘concept’, ‘intended’, ‘simulated’, or ‘pending validation’ must not be used as purchase evidence.