Recording settings that follow the project
A project decides whether its walkthroughs capture the screen or narration only, so a teammate recording your project produces the same kind of ticket you would, without having to remember a preference.
For Teams
Eat bugs together!
Live ticket updates, role-based access, audit logs, and project-level permissions, so your team can move fast without anyone losing track of who did what.
Customer reporting
Give customers a way to report. Give your team a way to act.
Install a separate widget for each project or client site. Reports land in that project’s intake column, and owners can see which widgets are off, waiting for detection, or live from one company-level view.
- One widget and destination board per project
- Cross-project setup and status for company owners
- Intake column keeps outside reports out of the team’s lane until reviewed
- Optional reporter email and custom questions
- No paid seat required for external reporters
- The same comments, board, audit, and MCP workflow
What you get on Team
Everything a dev team actually uses.
Bug reports inside every product
Install one widget per project. Customers report without seats, and each context-rich ticket stays inside the correct board and permission boundary.
An intake lane for outside reports
Widget reports land in an intake column, separate from the team’s own tickets. Review them there, move the real ones onto the board in bulk, and archive the noise before it reaches anyone’s queue.
Jira integration, owner-controlled
Send one ticket or a batch to Jira with annotated pictures, page context, and walkthrough video where it fits. Enable optional auto-send for new tickets. Only a company owner can connect Atlassian or change which Jira project a board maps to, so the destination is not something any member can quietly repoint.
Live ticket updates
Ticket moves, new comments, assignments, and capture-ready pings show up instantly across every Toado tab in your company. WebSocket-backed, Redis-replicated, no polling, no refresh button.
Multi-company, multi-project
Consultancies and agencies: one Toado account, many client workspaces. Each company gets its own isolated data, its own members, its own tickets.
Role-based access
Owner, member, and viewer roles. Viewers do not use a paid seat, and project-level overrides let you give a contractor access to one board without exposing the rest.
Threaded comments + @mentions
Discussion stays on the ticket. Mention a teammate, they get notified. Every comment is part of the audit trail.
A full audit trail
Every action is recorded: user, action, resource, timestamp, IP, user agent. Owners can review the trail for compliance or incident reviews.
Works with Jira
Nobody has to leave Jira for your team to use Toado.
Engineering captures, triages and fixes in Toado. Everyone else keeps planning in Jira. When a bug is real and someone outside the team needs to see it, export it and the Jira issue arrives with the screenshot and page context already attached, instead of a title and a shrug.
- Connect Atlassian once for the company, then map each project to its own Jira project and issue type.
- Running a company per client? Each one maps to that client’s Jira, with no chance of a ticket landing in the wrong tenant.
- Default labels on every export, so the Jira side stays filterable.
- Your redaction rules are re-applied to the exported text.
- Owner-only: connecting Atlassian and changing a mapping are restricted to company owners.
Specific updates in each direction. Where linked Jira status updates are enabled, Done and reopened issues update linked Toado tickets. Mapped ticket-type changes go from Toado to Jira. Comments and assignees stay in their own systems; moving a Toado ticket does not change Jira status.
Jira is included on Team, Business, and Enterprise. Business includes Widget Starter and 365 days of video history.
Who it fits
Built for the kind of team that actually ships.
Product & engineering teams
5–50 engineers where QA, design, and dev all file bugs. One board, one source of truth, one workflow to your AI coding agent.
Consultancies & agencies
One Toado account, a separate company per client. Guest seats for stakeholders, full seats for your team, tight permission boundaries.
Internal tools teams
Small, high-output groups inside larger companies. Quick bug capture from non-technical users, fast handoff to your AI coding agent for the fix.
Start a team in under a minute.
Start on the free plan. Team has no seat minimum, viewers are free, and you can change seats or cancel any time.