Sharing & publishing Pro
Requires ReadyTab Pro
Creating a share — all three modes — is a Pro feature. On free accounts the Share / Publish / Managed-boards controls are hidden in Settings → Spaces and shown locked (with a ✦) in a space's ⋯ menu. Receiving a share is always free: anyone can import a share code or subscribe to a managed board without Pro. See Free vs Pro controls.
ReadyTab has three ways to share a space, each aimed at a different audience. They look similar but behave very differently — picking the right one matters.
| Share code | Public board | Managed board | |
|---|---|---|---|
| What the recipient gets | Their own editable copy (a fork) | A read-only web page | A read-only tab inside their ReadyTab |
| Needs the extension? | Yes — to import | No — opens in any browser | Yes — to subscribe |
| Delivered as | A short code (CODE.SECRET) | A link (URL) | A token (+ optional password) |
| Stays in sync? | No — one-time copy | No — frozen snapshot | Yes — updates flow to subscribers |
| Recipient can edit it? | Yes (it's their copy) | No | No |
| Creator can update it later? | Yes — same code, new imports only | Yes — same link, all viewers | Yes — pushes to all subscribers |
| Encryption | End-to-end (license-derived secret) | End-to-end (secret in URL fragment) | End-to-end (token [+ password]) |
| Expiry | 30 days, or never | 30 days, or never | Until you unpublish |
| Manage from | Settings → Spaces → Shared boards | Settings → Spaces → Published boards | Settings → Spaces → Managed boards (publish & subscribe) |
The one-line mental model:
Share code = hand someone a starter they make their own. Public board = put a page on the web behind one link. Managed board = broadcast a live read-only board a team keeps seeing updated.
Share code — a one-time copy
A share code creates an encrypted snapshot of one space. Anyone with the extension enters the code and imports it as a new, fully editable space of their own. From that moment their copy and yours are independent — editing either one never affects the other.
Because it's a fork, updating a code only changes what future imports receive — people who already imported keep their copy untouched. (There's no way to push into a copy someone already owns; that would be collaboration, which share codes are not.)
Workflow example — onboarding starter
- You build a “Design team links” space.
- Settings → Spaces → Share this space → you get a code like
QA7B4SNG.1A2B…. Optionally name it and set it to never expire. - You paste the code into your team wiki.
- A new teammate opens Settings → Spaces → Import from code, pastes it, and gets their own copy to customize.
- Weeks later you add three more links. Open Settings → Spaces → Shared boards → ⋯ → Update code. The code stays the same, so the wiki link still works — and new teammates now get the improved version. Existing teammates keep their personalized copies.
Public board — one read-only link, no extension
Publishing turns a space into a frozen, read-only web page that anyone can open in a browser — no extension required. The recipient sees a standalone reader page that renders your board as designed.
Unlike a share code, there's a single link everyone opens, and when you update it, every viewer sees the new version (the link never changes).
What gets published
Launcher buttons and custom CSS are stripped, and clipboard content is excluded unless you explicitly opt in. The snapshot is encrypted in your browser; the decryption secret lives in the link fragment, so treat the link like a password.
Workflow example — a public resource page
- You build a “Free SEO tools” space.
- Settings → Spaces → Publish → choose a title/description and copy the link.
- You drop the link in your bio / a blog post. Visitors open it in any browser.
- You add a new tool to the space, then Settings → Spaces → Published boards → ⋯ → Update snapshot. The link is unchanged, and everyone who opens it now sees the new tool.
See Public boards for the full publish flow.
Managed board — a live, read-only subscription
A managed board is published from a source space and handed out as a token. People who subscribe get it as a read-only tab inside their ReadyTab that stays in sync: when you update the source and republish, their tab updates too. Boards can be password-protected.
This is the only mode where the recipient keeps getting your updates in place — ideal when a team should all see the same canonical board, always current, and never edit it.
Workflow example — an agency’s canonical board
- An agency builds a “Client portal” space and publishes it as a managed board from Settings → Spaces → Managed boards, bound to that source space.
- They send each client the token (and a password, if set).
- Each client opens Settings → Spaces, enters the token, and the board appears as a read-only tab with a sync indicator.
- The agency updates the source space and republishes; every client’s tab syncs to the new version — no new token, no re-import.
See Managed boards for subscription details.
Which one should I use?
- “They shouldn’t need to install anything.” → Public board.
- “Give them a starting point they’ll make their own.” → Share code.
- “A team should all see the same board, kept current, read-only.” → Managed board.
Not sharing — syncing your own boards
If you just want your own dashboard mirrored across your devices, that's Cloud sync, not a sharing mode.