Laya terminology
A glossary of the words Laya uses — workspaces, handles, boards, mirrors, master boards, sync terms and more.
Last updated
A quick reference for the words you will meet across Laya and this Help Centre. Each entry links to the article that covers it in depth.
| Term | Meaning |
|---|---|
| Workspace | The top-level container for boards, members and settings. Comes in two fixed kinds: Personal (private) and Team. A few older labels call a workspace an "org" — for example the command palette's "Go to Orgs". See Workspaces explained. |
| Handle | The short name in a workspace's URL — /{handle} for a team workspace, /personal/{handle} for a personal one. People have @handles too. |
| Board | Where work is planned and shipped, at /{handle}/{boardCode}. See Board anatomy. |
| Native board | A Kanban or Scrum board created in Laya, with the full feature set. See Creating and editing work. |
| Connected (mirrored) board | A board mirrored into Laya from Jira, Azure DevOps, monday.com, GitHub or GitLab, kept in two-way sync with its source. See Integrations overview. |
| Master board | A board that combines several sources — connected boards and native Laya boards — into one Laya-native view. See Master boards. |
| Work item / card | A single piece of work on a board. The product UI often labels work items "issues". |
| Swimlane | A horizontal grouping of cards on a board. Grouping options are None, Source board, Epic, Assignee, Priority and Sprint. See Views, filters and grouping. |
| Sprint | A time-boxed iteration on a Scrum board, managed from the board's Sprints and Backlog pages. See Backlog, sprints and epics. |
| Epic | A larger container that groups related work items; an epic can belong to an initiative. See Backlog, sprints and epics. |
| Initiative | A strategic container that owns epics and tracks health, confidence and progress, shown on the Roadmap. See Docs, Roadmap, Initiatives and Calendar. |
| CRM | Laya's built-in customer-relationship area, opened from the sidebar's CRM entry, with sections covering records such as accounts, contacts, leads, deals, campaigns and reports. Team workspaces only — personal workspaces do not show it. |
| Saved view | A captured board state — filters, grouping, sort and layout — listed under Views and pinnable to the sidebar. Board Studio's separate "Saved Views" tab stores appearance only. See Saved views and Insights. |
| Mirror | Laya's durable, synced copy of a connected board's work items — their core mapped fields, such as title, status, priority, dates and description. Comments are read live from the source rather than stored. Deleted when you disconnect the board. See Mirror vs import. |
| Import | A one-off copy of work into Laya, as opposed to a mirror that stays in sync. See Mirror vs import. |
| Two-way sync | Changes flow in both directions — an edit in Laya lands in the source tool, and an edit there lands in Laya. See How two-way sync works. |
| Source of truth | The system that owns the record. With connected boards, your existing tool remains the source of truth and Laya holds the mirror. |
| Board Studio | The per-board customisation drawer — theme, columns, cards, effects, the external share view and appearance presets. See Board Studio. |
| Public link | A read-only, no-account-needed share of a board, doc or roadmap. See Sharing boards publicly. |
| App-link | The connection between the "Laya Board for Jira" app and a Laya workspace, approved by entering a short device code. See Laya Board for Jira. |
Was this page helpful?
Still stuck?
Contact supportEmail support@laya.net — include what you expected, what happened, and a link to the affected board or item so we can help quickly.