Laylight + Confluence

What Laylight reads

Spaces and pages you connect, including page bodies, labels, authors and version history.

Access is read-only and scoped to what you connect. Laylight does not write to, modify or delete anything in Confluence.

What it adds to your context

Documented process: runbooks, policies, architecture notes and the record of who wrote them and when they were last touched.

How it works

You authorise Atlassian access and scope Laylight to specific spaces. Version history is read alongside content, which is what allows Laylight to flag that a runbook has not been updated since the system it describes changed. Labels and space structure are used as signals of what a page is for, so a policy is not treated as interchangeable with a meeting note.

Because Laylight resolves entities across every connected system, a Confluence answer is not limited to Confluence. The same customer, project or person referred to here is understood to be the same one referred to in the other systems you connect, so an answer drawn from Confluence can be cross-checked against the document, ticket or thread elsewhere that describes the same thing.

What you will be able to ask

• What is our documented process for this?
• Which runbook applies here?
• Has this page been updated since the change it describes?
• Who wrote this policy, and is that person still the owner?

Each answer names the Confluence record it came from, with its timestamp, so you can open the source and check it rather than taking the summary on trust.

How the connection is authorised

You connect Confluence through its own OAuth flow and choose the scope Laylight may index. Laylight never receives your Confluence password, stores its access token encrypted, and loses access the moment you revoke the connection. See Security for the full detail.

Availability

Laylight is pre-launch and connectors are rolling out to waitlist customers. Join the waitlist to get access to the Confluence integration, or see all integrations.