Floumy Documentation

Build in Public

Share selected project areas through public links while keeping editing inside the authenticated workspace.

What Build in Public Does

Build in Public lets you publish read-only project views through public URLs.

It is configured per project and is designed for:

  • Transparent customer updates
  • Public roadmaps
  • Shared progress views
  • Community-driven requests and issue intake

Where to Configure It

Open the project’s Build In Public settings page.

The screen includes:

  • A master public-pages toggle
  • Individual toggles for each supported area
  • A button to open the public page when at least one area is published

Public Areas You Can Share

Depending on project settings, you can make these areas public:

Public areaNotes
IssuesPublic issue board and issue detail pages
RequestsPublic request board and request detail pages
OKRsPublic project objectives and key result views
RoadmapPublic roadmap and initiative detail views
Active WorkAvailable when cycles are disabled
Active CycleAvailable when cycles are enabled
CyclesAvailable when cycles are enabled

How Public Access Works

Public pages are meant for viewing, not full workspace editing.

Public visitors can:

  • Browse the published areas
  • Open detail pages
  • Follow public progress links

Authenticated users can additionally:

  • Submit public issues
  • Submit public requests
  • Add comments where comments are available

Indicators in the Workspace

When an area is public, Floumy surfaces that state in the app:

  • Sidebar badges for public project sections
  • Project-card badges on the organization Projects page

These markers make it easy to see what is externally visible.

Good Rollout Pattern

  1. Publish Roadmap first if you want to share direction.
  2. Add Requests if you want structured public feedback.
  3. Add Issues if you want customer-facing bug reporting.
  4. Add OKRs, Cycles, or Active Work only if you are comfortable sharing operating detail.