Shipnoted
Start free
ProductDesignPricingCompareDocsSign in

Docs

Import, export, team and limits

Switch in a minute, take everything with you, delete one person, set how long details are kept, and run the team.

Import in a minute#

Open Import in the dashboard. Pick the tool you are leaving and paste an API key (it is used for the import only and is never saved). The page reads your board one page at a time, with a progress bar, and you can stop and carry on any time.

  • Canny (Settings, API): posts with their score, status, ETA and author; optionally who voted (with emails, so they hear when it ships), public comments, and your changelog entries as published releases. Internal and private comments are never copied.
  • Productboard (Workspace settings, Integrations, Public API): features become roadmap requests with status and timeframe; customer notes optionally too. Mostly internal, so it arrives hidden by default.
  • Featurebase (Settings, API): posts with votes, status and author. If a key import ever misses something, upload your Featurebase export file instead.
  • GitHub Releases: a repository’s published releases become changelog entries, dated as they were.
  • Any CSV or JSON file: columns are matched by name (title, details, status, votes, author, email, created).

Every imported item remembers where it came from, so running an import again adds nothing twice. Tick Hide what I import and everything arrives in the Archived lane, off your public board, until you restore what you want. Nobody is emailed by an import.

Export everything#

Data and privacy has two buttons (owners and admins): one JSON file or a zip of CSV spreadsheets. Both hold the same data: requests, every vote (with plan, revenue and company), comments, releases and translations, subscribers, the history of each request, the team, saved views and webhook endpoints. Left out on purpose: API keys, signing secrets, tokens, the capture address and attached screenshots. Downloads are limited to a few an hour and every one is in the audit log. Spreadsheet cells that begin with =, +, - or @ get a leading apostrophe, so opening the file cannot run a formula.

Delete one person#

On Data and privacy, look a person up by email. You see what is held: their subscription, votes that carry their email, requests they posted, and emails sent to them. Erasing removes the subscription, the sent emails and queued notices, and any webhook payload mentioning them. Their votes stay as anonymous votes (no email, company or attributes, and a fresh random voter key), so counts and revenue totals do not change; requests they posted stay without their name and email, unless you tick delete those requests too.

Comments carry only the display name they were written under, not an email, so they cannot be found by address; search the name on the feedback page. People can also ask for themselves: every public page has Delete my data. We email a link to the address and nothing is erased until it is followed, so nobody can erase (or probe) someone else’s data. Each erasure is recorded with a one-way hash of the address, never the address itself.

Retention#

By default a project keeps everything until you delete it. In Data and privacy you can choose to remove names, emails and companies from requests and votes older than 90 days, 6 months, 1 or 2 years (the requests and vote counts stay), and to delete people who unsubscribed after 7, 30 or 90 days. It runs nightly, and Apply now runs it at once. Removing a voter’s email means we can no longer tell them when their old request ships. Always on regardless: sent-email records after 90 days, webhook delivery logs after 14 days, activity history after a year, notifications after 90 days.

SSO and SAML#

Sign-in today is an emailed link or a password, with roles and an audit log. SSO and SAML are for Team workspaces, and we build them when a Team customer asks, so yours is built with you. Ask from Data and privacy; it reaches us directly.

The inbox and keyboard#

Feedback is an inbox built for working through quickly. Everything you do shows at once and is saved in the background; if saving fails it is put back and you are told. Press ? on the page for this list.

j / kMove down / up. Shift with them (J / K) adds to the selection.
x, ⌘ASelect the row, or all rows
sSet status from a list you can type in. 1 to 5 set it directly.
aAssign to a teammate, from a list you can type in
eArchive (or restore, in the Archived view)
mMerge the selected requests into the one with the most votes
zUndo the last change. It also works while it is still saving.
EnterOpen the request
/Search
g then i, n, r, t, l, a, s, hJump to the inbox, notifications, releases, themes, the loop, activity, settings, overview, from any page

The lanes above the list are Inbox, Mine (assigned to you), Unassigned and Archived, with the filters (status, tag, customer segment, sort, search) stacking on top of them.

Assign, archive, merge, split#

  • Assign a request to a teammate. They are told, and start following it. Assigned requests show the person’s initials in the list and can be filtered with Mine.
  • Archive what needs no answer (spam, duplicates you do not want to merge). An archived request leaves the inbox, the public board and the widget, takes no new votes, and keeps its votes, its page and its history. Restore it from the Archived lane.
  • Merge requests that are the same wish: select them and press m. Votes move to the keeper with the plan, revenue and company behind each one, so nothing is lost. Merges can be undone, from the toast or from either request’s page, and the votes go back where they came from.
  • Split a request that asks for two things: on its page, give the second one a title, tick the comments that belong to it, and it becomes its own request with the same author. The original keeps its votes: only people who want the new thing should vote for it.
  • Internal notes are for your team only. Mention a teammate with @name (the start of their email) and they are told. A private note never reaches a follower who was not mentioned.
  • Every request has a history: who posted it, changed its status, assigned it, replied, merged or shipped it. The Activity page shows the same for the whole project, filterable to what you did.

Viewers can look at everything and change nothing; members and above can do all of the above. The audit log (owners and admins) records the changes that matter to the account.

Saved views#

Set up the filters you use (assigned to me, Planned, Enterprise customers, by revenue) and press Save this view. It becomes a chip above the list. Yours are private; owners and admins can share one with the whole team. A view only stores filters, never data, so it is always current.

Notifications#

The bell shows what needs you: requests assigned to you, @mentions, and replies or status changes on requests you follow (assigned, replied to as the team, or mentioned on). It updates by itself every 30 seconds and the moment you come back to the tab. Each notification can also come by email; a busy thread is one email and a growing badge, not twenty. Choose what you hear about, per project, on the Notifications page: new requests are off by default, and email can be switched off while the bell stays on. You are never told about your own actions.

The command palette#

Press ⌘K (or Ctrl+K) anywhere. Requests, releases and pages are found as you type, from a list kept on your machine, so there is no wait. It also knows where you are: on a request it can set the status, assign, archive or follow it; in the inbox it does the same to your selection. Saved views and the inbox lanes are in it too.

Team and roles#

  • Owner: everything, including billing and deleting the project.
  • Admin: everything except billing. Manages the team, API keys, webhooks and connections.
  • Member: writes releases, triages feedback, edits the design.
  • Viewer: can look at everything and change nothing.

Images in release notes can be pasted, dropped or uploaded from the editor (JPEG, PNG, WebP and GIF, up to 4 MB each), and each release gets its own share image for X, LinkedIn and Slack previews. Replies can be marked as internal notes: your team sees them, the public board and the API never do. The Activity page records who published, deleted, merged, invited or connected what, kept for a year. A Monday digest email summarises the week for the whole team; turn it off in Settings.

Email to feedback#

On Pro and Team, send or forward any email to feedback+your-slug@shipnoted.com and it becomes a request: the subject is the title, quoted replies and signatures are cut from the body, and the sender is attached, so they are told when it ships. The same message never becomes two requests. Where the AI key is set, each email is read the way a person would: newsletters, receipts and out-of-office replies are skipped, and for a forwarded message the customer who wrote the forwarded part is the author, not the teammate who forwarded it. Set a forwarding rule in your support inbox (for example on a feature-request label) and your board fills itself.

Limits#

  • Free: 1 project, 100 subscribers, 3 AI drafts a month, badge shown.
  • Pro: 2,500 subscribers, 60 AI drafts, no badge, custom domain, scheduling, GitHub, API, webhooks, MCP, translations, email to feedback, screenshots.
  • Team: 5 projects, unlimited teammates, 15,000 subscribers, 300 AI drafts.