Disconnecting safely
Pause sync, remove a mirrored board or disconnect a provider — exactly what is kept, what is removed, and what never changes.
Last updated
On this page
You can dial sync down in stages — pause it, remove a single mirrored board, or disconnect the provider entirely. At every stage, Laya only ever touches its own copies: disconnecting never deletes or modifies anything in the source tool.
Pause before you disconnect
If you only need a break from syncing, pausing keeps every link intact so you can resume later:
- Per board — Board settings → Integrations tab lists each provider with a sync toggle. As the setting explains: "Turning a provider off pauses syncing for all linked issues — the links stay, so turning it back on resumes where it left off." State chips read Connected, Paused or Not connected.
- Per connection — the Polling toggle in the connection's Settings tab stops background pulls from the provider while leaving everything else in place.
- Per issue — Jira-linked issues offer Pause sync and Resume sync in the issue panel; resuming re-pulls the latest from Jira. (The panel's own hint recommends pausing over Remove link, because pausing keeps the link.)
Remove a single mirrored board
From the connection's Boards tab, Remove stops mirroring one board. The confirm dialog ("Remove mirrored board?") spells out the effect: mirroring stops and Laya's cached items for that board are removed — the source tool itself is untouched, and you can re-mirror the board at any time.
What disconnecting does
Disconnecting lives on the connection's Settings tab, behind a confirm dialog. What happens depends on the provider:
| Mirrored boards and cached items | Native boards and imported issues | The source tool | |
|---|---|---|---|
| Jira | Removed — every mirrored Jira board and its cached issues are deleted from Laya | Kept — native boards and imported issues remain, just unlinked | Untouched |
| Azure DevOps, monday.com, GitHub, GitLab | Removed — the connection, its mirrored boards and their cached items are deleted from Laya | Kept — as the dialog puts it, "Existing Laya boards are kept; their external mirror just goes inert." Imported issues remain ordinary Laya issues, just unlinked | Untouched |
Revoking access on the provider side
Disconnecting removes the stored credentials from Laya (they are held encrypted while connected). If you also want to revoke access at the source — good hygiene when off-boarding — do it in the provider:
- Jira / Atlassian — revoke the API token or the app authorisation in your Atlassian account settings.
- Azure DevOps — revoke the personal access token in User settings → Personal access tokens, or the app consent for Microsoft sign-in.
- monday.com — regenerate or revoke your personal API token under Profile → Developers → My access tokens.
- GitHub / GitLab — delete the personal access token, or revoke the OAuth authorisation, in each platform's settings.
For the full list of what each connection was granted, see Provider permissions and scopes.
Email support@laya.net — include what you expected, what happened, and a link to the affected board or item so we can help quickly.