Core Concepts

Understand the key building blocks of Velocity.

Workspace

A workspace is the top-level container for your organization. It holds all teams, issues, projects, cycles, and documents. Each workspace has a unique URL slug and its own billing plan. Members are invited to the workspace level.

Team

Teams group people who work together. Issues and cycles belong to a team. Common setups include teams per squad (“Frontend”, “Backend”) or per function (“Engineering”, “Design”).

Issue

An issue is a unit of work — a bug, feature, task, or anything your team needs to track. Each issue has:

• Identifier — auto-generated like ENG-42
• Status — Backlog, Todo, In Progress, Done, Cancelled
• Priority — None, Low, Medium, High, Urgent
• Assignee — the person responsible
• Labels — tags for categorization
• Description — rich-text body with Markdown support

Project

A project groups related issues toward a larger goal. Projects have milestones with target dates, a status (Planning, Active, Paused, Completed, Cancelled), and a progress bar computed from their issues.

Cycle

A cycle is a time-boxed iteration (like a sprint). Cycles have a start date, end date, and a set of issues. Velocity generates daily snapshots and a burndown chart to track progress.

Document

Documents are rich-text pages with a Tiptap editor. They support slash commands, code blocks with syntax highlighting, task lists, images, and more. Documents are organized in a hierarchical tree with parent/child relationships.

View

A view is a saved filter and sort configuration. Create custom views like “My open bugs” or “High priority backlog” and switch between them instantly.

Integration

Integrations connect Velocity to external tools. GitHub links PRs and commits to issues, Slack sends notifications, and X lets you post updates. Webhooks allow any external service to receive events from Velocity.