A reference board is usually a conversation. These are the parts that let the conversation happen on the board instead of in a chat thread that nobody can find three weeks later.
Availability
Real-time collaboration and share links are included from the Pro plan. Comments, voting and the timer are available wherever the board is.
When several people have the same board open you see each other's cursors, and objects update as they are moved. There is no save button and no “someone else is editing” lock.
Presence is per board, not per workspace, so the participant list tells you who is actually looking at this thing right now.
A comment pins to an object rather than floating in a sidebar. Replies form a
thread, @ mentions notify a colleague, and a thread can be resolved
once it is dealt with — or reopened when it turns out it was not.
Resolved threads stay attached to the object. The reason a decision was made is usually more valuable than the decision.
Start a voting session and everyone places dots on objects: click to add one, Alt + click to take one back. The results panel ranks the objects by votes.
It is the fastest way to get from twelve directions to two without a meeting about the meeting.
A countdown everyone in the session sees, with an optional label so people know what it is for. For timeboxing a critique, a retro column or a silent-writing round.
Step through pinned views or frames with the interface out of the way. The board stays live — you can annotate mid-presentation without leaving the mode, which is the point of presenting from a board rather than exporting slides.
A read-only share link lets someone view a board without an account and without taking a seat. This is the normal way to put work in front of a client.
There is also an embed snippet, for putting a board inside your own documentation or an intranet page.
Treat a share link as public
Anyone holding the link can view the board. Access tokens are managed on the server and can be revoked, so if a link escapes, revoke it — changing the board does not invalidate a link that is already out.
Boards keep their history. You can look at an earlier state and restore it, which covers the case that no amount of careful process prevents: somebody reorganised everything on a Friday afternoon.
Edits made without a connection are queued and reconciled when it returns. Where an automatic merge would not be safe, Ceyu keeps both versions rather than silently discarding one, and tells you it did. More detail in Storage, sync & encryption.