Security
Who can see what
Access to your website requests is set per person and per website. Sign-in can be protected with a second step, and private details can be kept out of screenshots.
Roles
What each role can do
A role sets what someone can do. Guests and viewers can also be limited to the websites that concern them, so a client with two sites and an agency with twenty can share one Bugpot.
A viewer can be allowed to comment and reply, one person at a time. Private notes and internal tasks are never shown to guests or viewers.
| Viewer | Guest | Member | Admin | |
|---|---|---|---|---|
| Read requests and replies | Yes | Yes | Yes | Yes |
| Send requests and comment | No | Yes | Yes | Yes |
| Change status, priority and who is on it | No | No | Yes | Yes |
| Write private notes | No | No | No | Yes |
| Invite people and set their access | No | No | No | Yes |
Sign-in, records and privacy
- Two-step sign-in
- Add a code from an authenticator app as a second step. Ten recovery codes cover a lost phone.
- Passkeys
- Sign in with a passkey, such as the fingerprint or face unlock on your device.
- Sign-in links
- Prefer no password? Ask for a sign-in link by email.
- A record of activity
- Owners and admins can read an audit log and export it as a spreadsheet file.
- Private details out of screenshots
- Parts of a page can be listed once for a website. They are blurred before every screenshot is taken.
- The button, by invitation
- The Feedback button can be limited to invited people, who sign in with a link sent to their email.
Already have an invite?
Sign in to see the requests for your website. Bugpot is invite only, so if you would like it on your site, write to hello@bugpot.io.
Sign in