FloumyWelcome to the end-user documentation for Floumy.
Floumy combines planning, delivery, feedback, public sharing, and developer workflow data in one workspace. The product is organized around a few connected layers:
| Layer | Purpose |
|---|---|
| Organization | Your company or team space. It contains members, org settings, org-level objectives, and projects. |
| Project | The main delivery workspace. Each project has its own planning, execution, feedback, public-sharing, and optional code settings. |
| Objectives and Key Results | Strategic goals and measurable outcomes. Projects can also link to org-level objectives. |
| Roadmap | Milestones and initiatives that connect strategy to planned delivery. |
| Cycles or Active Work | Your execution view. Projects can use time-boxed cycles or a continuous active-work model. |
| Work Items | The units of execution. Work items can be assigned, estimated, linked to initiatives, and connected to issues. |
| Requests and Issues | Customer feedback and bug tracking. Both support comments. Requests also support voting. |
| Pages and Audit Log | Internal documentation and recent activity. |
| Build in Public | Read-only public views for selected project areas. |
| Code and AI | Optional repository connections, delivery metrics, AI assistants, and MCP server access. |
How Floumy Fits Together
- Create an organization and add one or more projects.
- Define org-level objectives if you want a shared strategic layer across projects.
- Create project objectives and key results for the current quarter or later timelines.
- Turn those goals into roadmap initiatives and milestone dates.
- Deliver work through cycles or active work items.
- Capture incoming requests and issues, then connect them back to initiatives and work items.
- Share selected areas publicly if you want transparency with customers or your community.
- Connect GitHub or GitLab if you want repository metrics in the same project workspace.
Main Navigation
The project sidebar changes based on project settings:
| Area | When it appears |
|---|---|
| Objectives | Always |
| Roadmap | Always |
| Active Cycle or Active Work | Always, but the label depends on whether cycles are enabled |
| Cycles | Only when cycles are enabled for the project |
| Pages | Always |
| Code | Only when code integration is enabled for the project |
| Issues | Always |
| Requests | Always |
Numeric shortcuts follow the visible sidebar order, so the key assigned to an area can change when cycles or code are turned on or off.
Recommended Reading Order
- Getting Started for account setup, sign-in, project creation, and keyboard shortcuts.
- Organization and Projects for roles, members, org settings, and project configuration.
- Objectives and Roadmap for strategic planning.
- Cycles and Work Items for execution.
- Issues and Requests for feedback loops.
- Pages, Audit Log, and Collaboration for internal communication.
- Build in Public for public sharing.
- Code and AI for repository integrations and AI tooling.
Key Concepts to Remember
- Org objectives sit above projects. Project OKRs can link back to them.
- Initiatives connect roadmap planning to key results and requests.
- Work items connect execution to initiatives, cycles, and issues.
- Requests are best for demand and prioritization. Issues are best for defects and troubleshooting.
- Public pages are read-only views of selected project areas, but authenticated users can still submit public requests, issues, and comments where those screens allow it.