Get started
Quickstart
Create a workspace, invite teammates, and create your first issue — the five-minute path from sign-up to a working board.
Last updated
Planoda is one workspace that replaces a separate tracker, board, and doc: keyboard-first issues, Trello-style boards, roadmaps, no-code automations, and AI triage, all on one schema and one permission model. This guide takes you from a fresh sign-up to a working board with a few real issues on it.
You will need an email address. No credit card is required to start on the Free plan.
1. Create your workspace
Sign up at the marketing site and follow the onboarding flow. You will name your workspace (this becomes your workspace slug), then create your first team. A team is the unit that owns issues, boards, and cycles — most companies start with one team per squad (for example, Engineering, Design, Support).
Every team gets a short key (for example, ENG). Issues are numbered per team, so you will see identifiers like ENG-1234 throughout the product.
2. Invite your team
Open Settings → Members and invite teammates by email. Roles control what a member can do; tenant isolation is enforced in the database with Postgres row-level security, so a member can only ever read or write data inside workspaces they belong to.
The Free plan supports up to 10 members; Pro and above are unlimited.
3. Create your first issue
Press C anywhere to open the create dialog. Give the issue a title, set a priority and an assignee, and pick a workflow state (for example, Backlog or Todo). Hit Cmd/Ctrl+Enter to save. The issue gets a stable identifier and lands on your team's board.
Everything in the create dialog is keyboard-reachable — you can set the assignee, priority, project, and labels without touching the mouse.
4. Open your board
Each team has a board: columns are workflow states, cards are issues. Drag a card between columns to change its state, or reorder within a column to re-rank it. The board, the issue list, and any roadmap are three views over the same rows — there is no copy step and nothing to keep in sync.
Next steps
Group your work into a cycle to track what ships this week or sprint, then wire an automation so routine state changes happen on their own. The guides below walk through each in turn.