User guide

ProductOwner in ten minutes.

Everything you need to start, for every role. Inside the app, press ? for keyboard shortcuts, or Ctrl K (⌘ K on a Mac) to jump to any page or action.

1 · Getting started

Install it once. Someone on your team runs the installer on a server or computer (Download, about five minutes). The first person to open it becomes the admin.
Invite the team. In Settings → Team, add each person with their role. They get an email (or a link you share) and sign in from the browser or the apps.
Connect your code (optional). In Settings → Repository, connect GitHub or GitLab so each story gets its own branch and pull request.
Bring your work (optional). Settings → Import brings stories, people and history from Jira or Azure DevOps.

New here? Open Help → Take the tour for a one-minute tour made for your role.

2 · Roles

Each person has a role per project, and sees what that role needs, in words that fit the job.

ClientAsks for things, answers questions, approves designs, accepts work on the test site. Sees plain language, never the internals. Free on every licence.

Product ownerTurns requests into stories, designs screens, plans sprints, and decides what goes next.

DeveloperBuilds the story in its branch, reviews teammates' code, fixes bugs.

TesterRuns the test cases on each change and signs it off, or opens bugs.

DevOpsMerges, ships to staging and production, writes release notes, rolls back if needed.

AdminManages the team, settings, sign-in, email, licence and backups.

3 · A story's journey

Every piece of work moves through three phases. The colour of each column shows the phase; the small text under a column shows who it waits on.

DefineNew → Clarifying → Drafted → Designing → Awaiting approval → Ready. The client asks, the PO agent asks what's missing, the product owner writes the story and designs the screen, the client approves.

BuildIn progress → In review. The developer works in the story's branch; checks and reviews come back into the story.

DeliverIn testing → Staging → Live. The tester signs it off, the client accepts it on the test site, DevOps releases it.

Home always lists what's waiting on you. Start your day there.

4 · The board and its gates

Open a story to see its Next step: a short checklist of what's left before it can move on. When it's all ticked, the move button turns blue.
Gates stop half-done work from moving ahead: an approved design, green tests, an accepted test site. Nothing gets skipped by accident.
Filters and views: filter by squad, developer or type, switch to Waiting on me, and save your favourite filters under View → Saved views.
Search: press / anywhere. Custom fields can be searched too, for example impact:high.
Sprints: plan each sprint against the team's capacity and follow it on the burndown.

5 · For clients

New request: describe what you need in your own words. The team (and its AI helper) will ask if anything is missing; you'll find the questions on your Home page.
Review the design: you see the real screen before it's built. Approve it, or ask for changes.
Try it: when something is ready on the test site, try it, then accept it or tell the team what's wrong.
What's new: your Home page shows what went live, in plain language.
Chat: talk to the team in #with-clients, or message the product owner directly.

6 · Chat and meetings

Team chat: one channel for the team, one the client can read, one per squad, and direct messages. Type @ to mention someone; they're notified. Everything updates live.
Comments on a story: keep decisions next to the work. Tick Team only to hide a comment from the client.
Meetings: schedule standups, planning or client reviews from Meetings. Everyone joins from the browser or the apps, with screen share, chat, captions and recording.
Recaps: after a recorded meeting, the AI drafts a summary with decisions and action items; turn action items into stories in one click.

7 · Files on a story

Open a story and go to the Files tab. Drop screenshots, documents or designs there, or click Choose files (up to 25 MB each). Pictures show a preview. Tick Team only to keep a file from the client. Whoever added a file, the product owner or an admin can remove it.

8 · Apps and notifications

Desktop app (Windows, macOS, Linux): its own window and tray icon, with system notifications. Get it from Download.
Phone app (iPhone, Android): in Settings → My notifications, scan the QR code with the app to connect it to your server.
Choose how much you hear: in Settings → My notifications, pick my moves and mentions, everything, or nothing, for email and push. You can also get a daily email digest.
Offline: the apps open without a connection and show your last copy of the work; changes are sent when you're back.

9 · Reports and export

Reports shows what needs attention now, points done per sprint, and how long stories take from start to staging.
Activity on each story is the full history: every move, review and test run, with who and when.
Export: on the Backlog page, Export to Excel (CSV) downloads every item with its columns and your custom fields.

10 · For admins

Company sign-in: Settings → Sign-in connects Microsoft, Google, Okta or any OpenID provider.
Email: Settings → Email connects your mail server so invitations, notifications and recaps can be sent.
AI: Settings → Agents sets what the AI agents may do by themselves, and what always needs a person. AI uses your own API key, and can be switched off.
Licence: Settings → Licence shows the trial or licence, and where to add a new licence file. If it ends, nothing is deleted: ProductOwner becomes read-only until it's renewed.
Backups and updates: on the server, ./backup.sh saves the database and files (schedule it nightly and copy the backups elsewhere); ./update.sh installs the newest version and backs up first.

Need help? Contact support.