Confluence
Documentation and runbooks for operations and engineering
Polygrade integrates with Confluence for documenting the integration for your team's future reference, not claims data. Confluence is documentation and wiki software, often paired with Jira for engineering teams. It's a coordination layer around Polygrade's integration and exceptions, not a claims channel.
Confluence is documentation and wiki software, often paired with Jira for engineering teams. This isn’t where claim data lives, Confluence is where your team coordinates around Polygrade: documenting the integration for your team’s future reference.
What Polygrade does with Confluence
Your Forward Deployed Engineer documents the specific connector configuration, field mappings, and operational runbook for your Polygrade integration directly in Confluence, so the documentation lives where your team already looks for it.
Nothing about claim data, parts sourcing, or payment execution routes through Confluence. It’s purely operational, the coordination layer around the integration and around exceptions that need a person’s attention, not a channel for claim records themselves.
How the Confluence connection works
Integration documentation is written into a Confluence space your team provides during deployment.
This is set up once, early in deployment, alongside the rest of the Confluence configuration your team already maintains, it isn’t a separate ongoing integration to manage.
What stays in Confluence
Confluence continues to run exactly as it does for every other team and project already inside it. Polygrade adds one more source of notifications or tracked work, using the structure your team has already built.
Data handling and security
Anything Polygrade posts into Confluence, an escalation, a deployment update, is a notification about activity happening on your company-specific Polygrade instance, not a copy of underlying claim or customer data. Polygrade is SOC 2 compliant, with both Type I and Type II audits complete.
The claim recommendations behind any escalation posted to Confluence carry their own confidence level and audit trail inside Polygrade, independent of whatever your team tracks in Confluence.
Setting this up
A dedicated Forward Deployed Engineer sets up the Confluence connection early in deployment, working with whoever on your team owns that workspace.
Frequently asked questions about Polygrade and Confluence
Does claim data flow into Confluence?
No. Confluence is used for operational coordination, escalations, deployment tracking, documentation, not claim, parts, or payment data.
How does Polygrade connect to Confluence?
Integration documentation is written into a Confluence space your team provides during deployment.
Is Confluence required to use Polygrade?
No. Confluence is an optional coordination layer some clients use during deployment and ongoing operation; it isn’t required for Polygrade’s core claims functionality.
