Getting started
1. Sign in
Projectrr has no passwords. Go to projectrr.work and choose one of:
- GitHub or Google — one click, and the account you already use
- Magic link — enter your email, open the link we send
- Passkey — once you’ve added one from your profile page
Whichever you pick, you land in the app.
2. Create an organization
An organization is your top-level container — usually your company, or one
client. Give it a name and Projectrr derives a slug (acme-ltd) that appears in
every URL and in CLI commands.
Invite people from Settings → Members. Roles are owner, admin,
developer, member and viewer. Owners and admins configure the organization
— products, projects, statuses, workflow rules, integrations and membership.
Developers and members work the board: issues, comments and epic journals.
Viewers read. developer and member carry identical permissions, so pick the
label that suits your team; see roles for the full
breakdown. An action your role can’t take is shown disabled with a tooltip
naming the roles that can, so nobody has to find out by clicking.
3. Add a product
A product is a thing you ship — “ECOsmart”, “Marketing site”, “Mobile app”. Products hold projects, repositories, Trello credentials and epics.
If a product only ever needs one board, create it as a simple product: Projectrr makes a single default project for you and keeps it out of your way.
4. Add a project and its statuses
A project is one board with one issue-number sequence. Give it a name and a
short prefix (WEB, API) — issues become WEB-14.
New projects need statuses. Start from a template rather than building columns by hand:
| Template | Columns |
|---|---|
| Simple | Todo → In Progress → Done |
| Kanban | Backlog → Todo → In Progress → Done, plus Cancelled |
| Release Flow | Backlog → Todo → In Progress → In Review → On Staging → Done → Live, plus Cancelled |
Release Flow brings two rules with it: merging a pull request that references an issue moves that issue to On Staging, and publishing a release moves everything on staging to Live.
You can rename, recolour, reorder and add to any of them afterwards. See Core concepts.
5. Create issues
Create an issue from the board, the CLI or an AI assistant. An issue has a title, a markdown spec document, a status, a priority, an optional estimate, an assignee and watchers.
Open an issue and there’s a comment thread under the spec. Comments written here, from the CLI, by an assistant or on a linked Trello card all land in the same thread; commenting subscribes you to the issue.
The command palette (⌘K) is for finding things rather than creating them: it
searches products, projects and issues across the organization.
Drag it between columns and any workflow rules you’ve set up fire automatically.
6. Connect the rest of your stack
- GitHub — link repositories so commits, pull requests and issues tie back to Projectrr issues, and releases are tracked.
- Trello — link a board, map its lists to your statuses, import the cards you already have.
- The CLI —
prr login, then drive everything from a terminal. - MCP — connect Claude or Cursor so your coding agent works from the same board you do.
Next steps
- Group work that spans projects into an epic, and start its journal
- Automate the busywork with workflow rules
- Share a read-only roadmap or epic status report with a stakeholder — no account needed on their side