Laya Board for Jira — admin guide

This guide covers installing Laya Board from the Atlassian Marketplace, what you consent to, how the app binds to exactly one Laya workspace, the admin surfaces, sync behaviour, troubleshooting, and what happens on disconnect or uninstall.

Install from the Atlassian Marketplace

1. Install the appFind Laya Board for Jira on the Atlassian Marketplace and install it on your site. The app is free — licensing is disabled and no feature is paywalled.
2. Find it in JiraAfter install, Laya Board appears in each project's sidebar, in the Apps navigation, on the issue view, in ••• menus, in the command palette, and under Jira Settings → Apps → Laya Board.
3. Optionally link a Laya workspaceThe board works immediately with no Laya.net account. To unlock external boards, native boards, master boards, the Roadmap and guest sharing, link the site to a Laya workspace — the settings page shows the Connect wizard until the site is linked. The user guide walks through the pairing flow.

What you consent to at install

The app requests these Jira permissions, described in plain language:

• Read and write Jira issues and projects — render the board and apply your team's edits.
• See Jira users — show assignees and people pickers.
• App storage — keep the app's own settings (such as Board Studio styling and link state) in Forge storage on your site.
• Jira Software agile access — read boards and their column configuration so columns match your Jira board exactly; rank and order issues; move issues to the backlog; read and manage sprints; and epic read/write.
• Atlassian user-privacy reporting — not a data-access scope: it only enables a weekly compliance cycle that reports stored Atlassian account ids and relays erasure verdicts so Laya deletes them. An install with no workspace link stores no personal data.

You also consent to limited external egress: server-side calls to Laya's own hosts (laya.net, app.laya.net and their staging equivalents), plus images from those hosts and from static.klipy.com for the GIF picker. Because calling Laya.net is core to the product, the app is deliberately not an Atlassian "Runs on Atlassian" app.

One Laya workspace per install

Each installation binds to exactly one Laya workspace. The link is pinned to the installation itself, and Laya rejects a link token bound elsewhere — the settings page then shows "This Jira site is already connected to a different laya workspace." Re-linking an already-connected site is treated as a teardown and rebind, and requires both the connect and disconnect permissions.

Configuration surfaces

The settings screen is reachable from Jira Settings → Apps → Laya Board and from each project's settings sidebar (both show the same screen). Once linked it has a Jira sync tab plus one tab per connected external provider (Azure DevOps, monday.com, GitHub, GitLab — no empty tabs). The Jira tab contains:

• Laya.net connection — the linked Workspace, the Jira site and a Connected chip, plus Open Laya workspace ↗ and Disconnect from Laya.net.
• Write-back to Jira — controls whether edits made in Laya.net flow back into Jira through the app.
• Sync health — live status, counters and repair actions.
• Permissions — who on the site may use the higher-impact actions.

Write-back to Jira and the project allowlist

Write-back is fenced by a per-project allowlist. On a genuine first connect the allowlist is seeded with every project on the Jira site; after that, only the allowlisted projects can be written to, and an empty list keeps write-back off. Use Enable all projects or Choose projects / Edit projects (with Select all / Clear), then Save & register. The chip reads Bridge registered or Inactive, and Register write-back bridge / Repair write-back bridge are available as needed.

Sync health

The Sync health panel shows a Write-back on/off chip, write-back counts, active syncs, per-project Sync now buttons and recent activity, with a Refresh button. Dedicated red banners appear — each with a Repair or Reconnect button — when the workspace has disconnected on the Laya side, when "Inbound events are failing — Jira changes are not reaching Laya.", when write-back pings fail verification, or when Laya has no write-back bridge registered for this site.

Permissions panel

Three actions can each be set to All members or Admins only. The panel's own words: "By default anyone in your Jira site can do these. Restrict any to admins only."

How permissions work

• On the board itself, the app reads and writes Jira as the signed-in user — a user who cannot transition or edit an issue sees those controls read-only, or gets Jira's own rejection.
• The app writes under its own identity only for write-back from Laya, the initial backfill, and six agile backlog/sprint/rank operations — and each of those is fenced by either the project allowlist or a re-check of the caller's own Jira permission on the affected project, board, sprint or issues.
• Every app operation sits behind a declared authorisation gate (public, any member, admin, or policy-controlled).
• Board Studio settings are installation-wide per board, and writing them requires browse permission on the board's project.

How sync works with Laya.net

• Into Laya (event-driven): subscribed Jira events (issue created, updated and deleted; comment added and deleted) are filtered to the connected projects and delivered to Laya with the full issue payload — a change normally lands within seconds. Events caused by the app's own write-back are dropped, so there is no echo loop.
• Initial import (backfill): Laya orchestrates a paginated backfill, one page at a time; the board in Laya shows "Syncing via Laya Board app…" while items arrive.
• Out of Laya (write-back): Laya sends a signed ping to the app, which verifies it and applies the authorised change under the app's identity — so the Jira actor for Laya-originated changes is the Laya Board app by default. Members who link their own Jira access in Laya get a per-user toggle to have their edits attributed to them personally — see people and assignee matching.
• Outcomes: in Sync health, a write-back is terminally rejected for permission-style failures (and missing workflow transitions), and retried as an error for rate limits, server errors and network faults.

Troubleshooting

• "Duplicate board" or "sync broken" — check for a workspace mismatch first (see above).
• "Inbound events are failing — Jira changes are not reaching Laya." — click Repair. Repair re-registers the bridge and rotates its secret, which fixes both inbound delivery and failing write-back pings in one action.
• "The Laya.net connection is no longer valid" — the link was revoked or expired; reconnect from the settings page.
• "This app now points at a different Laya.net environment" — the app's environment changed; reconnect.
• "The Laya workspace disconnected this Jira connection" — someone on the Laya side disconnected it; reconnect if that was not intended.
• A temporary Laya.net outage never shows as disconnected — the app distinguishes real link breakage from unreachability.
• Non-admins who cannot connect see "Ask your admin to connect" pointing to Jira Settings → Apps → Laya Board.

If a problem persists after a repair and reconnect, contact support via Contact support in the app's Help & support menu, or email support@laya.net, with your site URL and the exact banner text you see.

Disconnect, reinstall and uninstall

• Disconnect from Laya.net? offers the checkbox "Also delete synced data in Laya (mirrored boards and issues; Laya-native boards are untouched)" — the confirm button reads Disconnect or Delete data & disconnect, and the purge runs first.
• Delete synced data is a separate typed-confirmation action: "This permanently deletes all Jira-mirrored boards and issues from your Laya workspace. Laya-native boards and your Jira data stay intact."
• If Laya.net cannot be reached during a disconnect, the app tells you the workspace token revoke is being retried automatically.
• Upgrades silently re-register the bridge to heal drift, but an upgrade can never resurrect a connection the workspace disconnected on purpose.
• Uninstall makes a best-effort revoke of the Laya-side link and purges all of the app's stored data on your site, including secrets and Board Studio settings. If Laya.net cannot be reached at that moment, the workspace token is not revoked and remains valid until revoked from the Laya workspace settings (tokens are honoured for up to a year) — so if you are decommissioning, disconnect from Laya.net first, then uninstall.

Differences vs the built-in Jira connector

If the app is installed, Laya's connect-Jira flow flags the site as Already connected via the installed app and recommends using that connection instead of setting up OAuth. See connect Jira for the connector path.