Publishing

Turn a view or a page into a public link. Anyone with the link can read it in their browser — no account, no sign-in.

Plan: Business and above

Useful for a public bug list, a customer-facing release page, a status view for a client who shouldn't be a workspace member, or a spec you want to send to someone outside the company.

What you can do

  • Publish a view (its work items) or a page (its content) to a public URL.
  • Publish from the Publish Center, or straight from a view's ••• menu.
  • Copy the public link, or open it to check what visitors see.
  • Unpublish at any time — the link stops working immediately.
  • See everything currently published in your workspace in one place.

Getting started

From the Publish Center

  1. Open the Publish Center from the app rail (the globe icon).
  2. Pick a project from the dropdown.
  3. Choose the Views or Pages tab.
  4. Flip the toggle next to the item you want to publish.

That's it. The row now shows Copy link and an open-in-new-tab icon.

📷 Screenshot: The Publish Center with a project selected, the Views tab active, and one view toggled on showing its Copy link action.

From a view directly

  1. Open a project's Views.
  2. Click ••• on the view → Publish to web.
  3. In the modal, click Publish to web.
  4. Copy the link, or click the external-link icon to open it.

The same modal is where you Unpublish later.

📷 Screenshot: The "Publish view" modal showing the generated public URL with Copy and Unpublish actions.

The public URL

Publishing generates a short, random, unguessable anchor and gives you a link like:

https://your-coco-kanban-host/p/kJ3xQm7Ab2

The anchor has no relationship to the view's name or ID, so the link can't be guessed from anything a visitor already knows. It is, however, a secret-in-a-URL: anyone who has the link can open it. There is no password, no expiry and no access log. Share it accordingly.

Re-publishing something you previously published reuses the same anchor rather than minting a new one.

What visitors see

A published view renders as a clean, read-only list of its work items — each with its identifier, title, priority and state — under the view's name and description.

A published page renders as its formatted content.

Visitors do not see: comments, attachments, activity history, assignees, the rest of the project, your workspace, or any way to sign in or edit. It's a one-way, read-only render.

A published view shows up to 250 work items. Drafts and archived items are always excluded.

Unpublishing

  • Publish Center: flip the item's toggle off.
  • From the view menu: open Publish to web → Unpublish.

The public link 404s immediately. If you publish the same item again later, it comes back on the same anchor — so an old link that someone kept will start working again. If that's a problem, don't re-publish it; create a fresh view and publish that instead.

Tips

  • Publish a view, not a whole project, when you only want customers to see certain work. Build a view with the filters you want, check it, then publish it.
  • The published content is live, not a snapshot. Change the underlying view or page and the public link reflects it on the next load.
  • Use the Publish Center periodically as an audit: it lists everything in the workspace that currently has a public link.

Limits & good to know

  • Views only apply their simple filters publicly. State and priority filters carry through to the public render. Assignee and label filters are not applied there — so a view filtered "assigned to Priya" may show more items publicly than it does inside the app. Check the public link before you send it.
  • Only views and pages can be published this way. Not cycles, modules, dashboards or work items.
  • 250 items max per published view.
  • Anyone with the link gets in. No password protection, no expiring links, no per-visitor access.
  • Unpublishing is instant, but anything already loaded, cached or screenshotted by a visitor is out of your hands.