Public Views

Share a read-only view of any workspace with anyone, even if they don't have a Blue account.


Public Views let you share a live, read-only link to a workspace with people outside of Blue. Great for client-facing roadmaps, public project trackers, shared hiring pipelines, content calendars, or embedding live data in your own website.

Every public view is read-only. Visitors can’t create, edit, or delete records, and they can’t see anything you haven’t explicitly exposed.

How Public Views Work

Public views are configured per workspace. Each public view has its own URL, its own visibility rules, and its own set of options. You can create multiple public views from the same workspace — for example, one for clients and one for the public roadmap — each showing a different slice of the data.

A public view only ever shows what you turn on. Fields, lists, and records that aren’t explicitly exposed are hidden from visitors entirely.

Read-only by design

Visitors cannot change data in a public view. No matter which options you enable, public views are always read-only.

Creating a Public View

There are two ways to create a public view:

  1. Open a workspace and click the Share button in the top right, then choose Public Views.
  2. Or go to Workspace Settings → Public Views and click Create Public View.

The full-page editor opens with a general settings panel on the left and a field permissions panel on the right.

General Settings

Name

A label for your public view, used only inside Blue to help you find it again. Visitors don’t see this name.

URL Slug

The slug that forms the public URL for this view. For example, a slug of roadmap produces a URL like blue.cc/public/your-org/your-workspace/roadmap.

Slugs must be unique within a workspace.

Password Protection

You can require a password before visitors can access the view. This is useful when you want to share a view with a specific group (a client, a partner, internal stakeholders) without creating Blue accounts for them.

Enterprise feature

Password protection is available on the Enterprise plan.

Options

Allow Filtering

When enabled, visitors see a filter toolbar and can slice the records themselves. When disabled, visitors only see the data as you’ve configured it.

Allow CSV Export

When enabled, visitors can download the records they see as a CSV file.

Enterprise feature

CSV export is available on the Enterprise plan.

Allow Opening Records

When enabled, visitors can click into a record to view its details. When disabled, records are displayed but not clickable.

Allow Search Engine Indexing

When enabled, Google and other search engines can discover and index the public view. Turn this off for private-but-unauthenticated sharing — the view will still work for anyone with the link, but won’t appear in search results.

View Types

Choose which view types are available to visitors and rename them to whatever makes sense for your audience. You can also drag to reorder how they appear in the view switcher.

Currently supported view types for public views:

  • Board — Kanban-style columns
  • Table — spreadsheet-style grid
  • Calendar — date-based view

Timeline and Map views are coming soon.

Record Visibility Filter

Scope the public view to just the records you want to share. Records that don’t match your filter conditions are completely hidden from visitors — they don’t know those records exist.

For example, on a client-facing public view you might filter to only show records tagged “Client Visible”, hiding internal tasks.

Leave the filter empty to show all records in the workspace.

Enterprise feature

Pre-applied record filters are available on the Enterprise plan.

List Permissions

Choose which lists in the workspace are visible to public visitors. Any list you don’t expose is hidden from the public view entirely.

Field Permissions

Choose which fields are visible to public visitors. This applies to both built-in fields (description, dates, assignees, tags) and custom fields.

Fields that aren’t exposed are hidden from every view — board cards, table columns, calendar tooltips, and the record detail panel.

Saved Views

Let visitors switch between multiple saved views without giving them the ability to create new ones. Useful when you want to offer, for example, a “By Status” grouping and a “By Assignee” grouping as two pre-built options.

You can also designate one saved view as the default — the one visitors land on when they first open the public view.

Pro feature

Exposing saved views is available on Pro and Enterprise plans.

Sharing Your Public View

Once your public view is saved, you have two ways to share it from the top of the editor:

Click Copy link to copy the public URL. You can paste this anywhere — emails, Slack, LinkedIn, your website.

Embed Code

Click Copy embed to copy an iframe snippet that embeds the public view directly into another site. Paste the embed code into your website, Notion page, client portal, or wherever you want the live view to appear.

The embedded view is fully interactive — it scrolls, filters, and opens records just like the standalone version.

Custom Branding

By default, public views display a subtle “Powered by Blue” mark. Workspaces on the Pro and Enterprise plans can hide this mark so the view looks like part of their own product.

Pro and Enterprise workspaces can also serve public views from their own custom domain instead of blue.cc. See white label for setup details.

Feature Availability by Plan

FeatureTeamProEnterprise
Create public viewsYesYesYes
Pick visible lists and fieldsYesYesYes
Choose and rename view typesYesYesYes
Allow filteringYesYesYes
Allow opening recordsYesYesYes
Toggle search engine indexingYesYesYes
Embed into other sitesYesYesYes
Expose saved viewsNoYesYes
Remove “Powered by Blue”NoYesYes
Custom domainNoYesYes
Password protectionNoNoYes
Pre-applied record filtersNoNoYes
CSV export for visitorsNoNoYes

Deleting a Public View

From the public view editor, click Delete in the top right. Deleting a public view permanently removes the public URL — anyone with the link will no longer be able to access it. The underlying workspace data is untouched.