Integrations overview

Laya connects to the tools your teams already use and mirrors their boards as live, editable Connected boards. Your work stays where it is — as the connect flow puts it, We never migrate your data. — and changes flow both ways, so an edit in Laya lands in the source tool and vice versa.

Why connect a tool

• Keep every team in its own tool. Engineering can stay in Jira or GitHub, operations in Azure DevOps, marketing in monday.com — Laya mirrors their boards without asking anyone to move.
• See everything in one place. Mirrored boards sit alongside your native Laya boards, and master boards can combine work from several sources into a single view.
• Edit from Laya. Connected boards are not read-only: dragging a card, editing a field or posting a comment writes straight back to the source tool.
• Nothing is migrated. Mirroring keeps a durable, synced copy of each item — title, status, assignees, dates and links — that lives only until you stop mirroring, so there is nothing to un-migrate later.

The five supported platforms

Laya has full mirroring connectors for five platforms. Each one has its own setup guide:

• Jira — mirror projects and issues with live sync, including sprints, epics and comments.
• Azure DevOps — mirror work items and boards, per project and team.
• monday.com — mirror boards and items, including most column types.
• GitHub — mirror repository issues and Projects v2 boards.
• GitLab — mirror project issues and issue boards, including self-managed instances.

Core concepts

Mirror or import. Mirroring keeps the source tool as the system of record and shows a live, editable projection in Laya. Importing copies items into Laya as native rows you own. Most teams start with mirroring — see Mirror vs import for an honest comparison.

Sync is two-way. Edits made in Laya are pushed to the provider immediately. Changes made in the provider flow back into Laya — instantly for Jira when a webhook or the installed app is set up, and on a background poll or a manual Sync now for the other providers. The details are in How two-way sync works.

What Laya stores. For each mirrored board Laya keeps a durable, synced copy of every item — title, status, assignees, dates, links and timestamps — so boards open instantly, kept until you remove the board or disconnect. Comments are read live from the source tool rather than stored, and attachments are not copied (on Jira they are view-only; only a one-off import copies attachments into Laya). Connection credentials are stored encrypted and are never shown again in the interface.

Connection health

Every connection has a Manage page showing a health state (Healthy, Degraded, Needs attention or Idle), the last sync time and a read-only sync log of recent inbound and outbound events. Health updates live, so a failing connection surfaces without a refresh. See Managing connections.

Safety: your source tool is never touched

Removing a mirrored board or disconnecting a provider removes Laya's synced copies and stops sync — it never deletes or modifies anything in the source tool. Native Laya boards and imported items always survive a disconnect. The full picture, including how to revoke access on the provider side, is in Disconnecting safely.

Things that are not data integrations

A few connected-sounding features are separate from board mirroring:

• Sign-in providers. "Continue with Google", "Continue with Microsoft" and "Continue with Slack" are sign-in options only — they do not sync any work. "Continue with Atlassian" and "Continue with Azure DevOps" are also sign-in options, and can optionally lead into connecting Jira or Azure DevOps afterwards. See Sign-in methods.
• Outbound webhooks. Workspace Settings has a Webhooks tab that sends Laya events (issue created, status changed, and so on) to endpoints such as Slack, Teams, Zapier or PagerDuty. That is Laya notifying other systems — not a board mirror.
• Calendar feed. The Calendar page can mint a public iCal URL for external calendar apps.
• GIF effects. The GIF picker in Board Studio effects is powered by a server-side GIF provider — an internal service, not a workspace integration.

Common mistakes

• Trying to connect without Admin rights. Connecting needs the connectors:manage capability — ask a workspace Admin.
• Expecting a migration. Mirroring copies nothing permanently into your ownership; if you want native Laya copies, that is an import.
• Assuming disconnect deletes source data. It never does — only Laya's synced copy is removed.
• Expecting instant push from every provider. Today only Jira has a working inbound webhook (plus the installed Laya Board for Jira app); the other providers rely on polling and Sync now.
• Connecting one Jira site to two workspaces. A workspace binds to one Jira site, and a site has one canonical shared workspace — see Choosing your setup.