Workspaces and boards
Can keeps structure to three levels: workspaces contain boards, boards contain columns and tickets. There are no sub-boards, swimlanes, or portfolios to configure.
Workspaces
A workspace is the unit of membership and billing identity — your team, your family, your side project. You can belong to any number of workspaces and switch between them from the workspace switcher in the left drawer.
Each workspace has:
- A name — display only, rename it any time.
- A slug — the URL segment (
can.randomfact.com/acme). 5 to 20 characters: lowercase letters, digits, and single hyphens. Admins can rename the slug from workspace settings; old links to the previous slug stop resolving. - Members — each with a role,
adminormember.
Roles
| Capability | Member | Admin |
|---|---|---|
| Read and edit boards, tickets, comments | Yes | Yes |
| Create boards | Yes | Yes |
| Create public boards / change board visibility | No | Yes |
| Invite, remove, or change roles of members | No | Yes |
| Rename the workspace or its slug | No | Yes |
| Delete a board, or restore one from the Trash | No | Yes |
| Delete a ticket, or restore one from the Trash | Yes | Yes |
| Delete forever from the Trash | No | Yes |
| Delete the workspace | No | Yes |
A workspace always keeps at least one admin — the last admin cannot be removed or demoted.
Invites
Admins create invite links from workspace settings. An invite link looks like can.randomfact.com/join/<workspace-id>/<code>, carries a role (admin or member), is single-use, and can have an expiration. Anyone who opens the link signs in with Google and lands in the workspace with that role.
Boards
A board is where work happens. Each board has:
- A key — 3 to 5 uppercase letters (
LAUN), used to build ticket ids (LAUN-42). - Columns — each with a name, an optional color, an optional WIP limit, and a category:
todo,in-progress,done, orwont-do. Categories drive the column's icon and how features like "hide old done tickets" decide what to fade out. - A backlog — tickets that are not in any column yet. The drawer shows a live count.
- An all-issues view — every ticket on the board in one filterable list.
- A Trash — the tickets deleted from the board in the last 30 days, ready to restore. See Tickets.
Board visibility
- Private (default) — only workspace members can see the board.
- Public — anyone with the link can read the board, including people who are not signed in. Writing still requires workspace membership.
Only admins can make a board public or take it private again. The board header shows a visibility badge so the current state is never a surprise.
Board settings
Open a board's settings from the board header. From there you can rename the board, change visibility (admins), delete the board (admins — see below), adjust view settings (hide done tickets older than a chosen number of days, hide Won't Do columns), and connect AI agents — see Hosted MCP server.
Deleting a board
Deleting a board moves it, with everything on it, to the workspace's Trash for 30 days: it leaves the board list and its links stop working, but nothing on it is lost. An admin restores it from Workspace settings → Trash, or deletes it forever from there. After 30 days it is deleted for good.
A board in the Trash keeps its key, so a new board can't use the key until the old one is restored or deleted forever.
Import and export
Every import creates a new board. It never adds tickets to a board you already have, and a key that is already used in the workspace is refused. Any workspace member can import, from Import board on the workspace page.
If an import fails, nothing from it is kept and its key is free again, so you can retry straight away. An import stops itself after about four and a half minutes rather than run into its time limit. While an import is running, its key is taken: another import, or a new board, with that key is refused until it finishes.
Can board export
Open a board's settings and click Download as JSON. The file holds the board's columns, tags, tickets, comments, history, and links. Attachments are not included.
To bring it back, choose the file under Import board. The board key is filled in from the file, and you can change it before importing. Ticket numbers are kept either way: ENG-142 stays ENG-142, or becomes OPS-142 if you import the board as OPS. When the key changes, mentions of the board's tickets in titles, descriptions, and comments change with it, so they still link to the right ticket. Mentions inside links and code are left as they are.
Images pasted into descriptions and comments are copied into the new board during the import, so everyone in the workspace you import into can see them, and they stay after the original board is deleted. An image is copied only if you are a member of the workspace it came from. An image that isn't copied keeps pointing at the original board's file: only members of that workspace see it, and only while that board exists. When the import finishes, Can says how many images it copied and how many it couldn't.
Linear CSV export
In Linear, an admin exports the whole workspace from Settings → Administration → Import/Export → Export CSV, and Linear emails a download link. A CSV exported from a single Linear view works too. Choose the file under Import board. Can reads the file, whatever it is named, and shows one row per Linear team: how many issues it has (and how many are archived), and how many columns and tags it will get. Untick the teams you don't want, then import.
- One new board per team. The board is named after the team, and its key is the team's key unless you change it in the team's Board key field.
- Numbers are kept.
ENG-142in Linear isENG-142in Can, orOPS-142if you import the team asOPS. A team whose key isn't 3 to 5 letters, or is already a board in this workspace, starts unticked until you give it another key, and two teams can't share a key. A team whose issue IDs are malformed or repeated can't be imported under any key. The preview says why. - Mentions follow a new key. When a team is imported under another key, mentions of its issues in titles and descriptions are changed to that key, from every team in the same run. Mentions inside links and code are left as they are.
- Archived issues are included, in the column of their status.
What the import does with the rest of an issue:
- Columns are built from Linear statuses, one column per status. Each column gets a category from its issues' Started, Completed, and Canceled dates: completed issues count as done, canceled ones as won't do, started ones as in progress, and the rest as to do. The column takes the category most of its issues have. Within a column, tickets are ordered by Linear priority, urgent first, then by issue number. The order you dragged issues into in Linear isn't in the CSV.
- People are matched by email to workspace members. An assignee who isn't a member leaves the ticket unassigned, and their email is kept in the ticket's description. A creator who isn't a member is kept the same way, and the ticket is recorded as created by you. The preview lists everyone it couldn't match, so you can invite them first.
- Labels become tags: up to 50 per team, most used first, and up to 10 per ticket. Labels that don't fit are listed in the description.
- Priority, estimate, project, cycle, due date, parent, and related, blocking, and duplicate issues have no field in Can, so when they're set they're listed under Imported from Linear at the end of the description. A related issue whose team is imported in the same run links to its ticket; any other is shown as plain text.
- Links to other Linear issues are rewritten to the issue's key (the new one, if you changed its team's) when that issue's team is imported in the same run.
[the CI ticket](https://linear.app/…/ENG-10/…)becomesthe CI ticket (ENG-10), and Can links that key to the imported ticket. A link into a team you leave out keeps pointing at Linear, as do links to projects, views, and issues outside the export. A plain mention of an issue in a team you leave out is shown as code, so it doesn't link to an unrelated board that has the same key. - Comments, and files attached to an issue outside its description, aren't in Linear's CSV, so they aren't imported.
- Images and files in descriptions are copied into Can during the import, while Linear's links to them still work. Those links expire, usually about a month after the export, so import soon after you export. The preview says how many files will be copied.
- An image (PNG, JPEG, GIF, WebP, or AVIF) is embedded in the description, as if you had pasted it.
- Any other file, SVG images included, is attached to its ticket as a download. Where the link was, the description says
(attached: report.pdf). A ticket holds up to 20 attachments. - A file that can't be copied keeps its link to Linear: its link has expired, Linear didn't send it, it's larger than 25 MB, its ticket already has 20 attachments, or Can couldn't save it. After the import, a message says how many files were copied and how many still point at Linear, and counts the ones Linear sent but Can couldn't save on their own, since those are a problem on Can's side.
- Once Linear's links have expired, the preview says so. To copy the files, export again from Linear and import that file instead.
- Long descriptions are cut so the whole description, including the Imported from Linear list, fits Can's limit of 50,000 characters. A note marks where the text was cut, and the preview says how many descriptions will be cut.