Managing connections

Every provider connection has a Manage page in your workspace settings where you can watch its health, browse mirrored boards, read the sync log and change connection settings.

Where to manage connections

Open workspace Settings and go to the integrations area for the provider (Jira, Azure DevOps, monday.com, GitHub or GitLab). Connection cards also appear on the workspace home's Connected tab with Import to Laya and Manage buttons. Each connection page has three tabs — Boards, Sync log and Settings — for every provider.

Connection health

The health card shows one of Healthy, Degraded, Needs attention or Idle, alongside the last sync time (for example "Synced 2m ago") and the most recent error message if something failed. Health updates live — you don't need to refresh. Jira connections also have a Test connection button that probes the site and reports "Connection healthy" or "Connection unhealthy".

The Boards tab

The Boards tab is a launchpad for everything mirrored through the connection. Each board row shows a freshness dot with its last synced time and descriptive chips (project type, item and column counts, and "In master:" when the board feeds a master board), plus actions:

• Open board → — jump to the mirrored board.
• Sync now — pull the latest items from the provider immediately.
• Board Studio — customise the board's appearance and sharing.
• Import to a master board — on Jira connections, send this board's issues into a master board.
• Remove — stop mirroring this board and delete Laya's cached items. The source is untouched and you can re-mirror at any time.

Use Mirror a project / Mirror a board (or + Mirror a board on the hub) to add more boards to an existing connection without re-authenticating.

The sync log

The sync log is a read-only, newest-first list of recent sync events. Each row shows a timestamp, a direction arrow (↓ from the provider, ↑ to the provider), the item involved, the action, and a state — queued, syncing, retrying, succeeded or failed — and expands to show the error message and payload. The log refreshes live as events happen. There is no retry button in this version; failed outbound edits are reconciled by the next inbound sync. See Sync health, logs and recovery.

The Settings tab

• Polling — a per-connection toggle for the background poll that pulls provider changes when webhooks are unavailable. Toasts confirm "Polling enabled" or "Polling disabled".
• Webhook URL — the inbound push address for this connection. For Jira, add it under Jira Admin → System → Webhooks to enable instant push. For the other providers the card is shown but instant push is not live yet.
• Refresh credentials — re-runs the connect flow to store fresh credentials.
• Disconnect — removes the connection. Read Disconnecting safely first.

Reauthorising a connection

OAuth tokens refresh automatically in the background. If a refresh fails permanently — for example the grant was revoked — the connection is marked as expired ("Jira authorization expired — reconnect required.") and stops syncing until someone with connectors:manage re-authorises via Refresh credentials or Re-establish connection. monday.com tokens never expire, but if one is revoked in monday.com the connection starts failing and needs a fresh token. If health stays on Needs attention after reauthorising, contact support@laya.net.

Multiple connections and sites

Azure DevOps, monday.com, GitHub and GitLab all support several connections in one workspace — use "Connect a different … connection" to add another organisation, account or namespace. Jira is the exception: one Jira site per workspace, by design.