Feature requests and bug reports

Every tenant has a feedback panel at Settings → Feedback / Bug report. Use it for product feedback, bug reports, scanner false-positive trends, or "this could be better"-type notes. Faster than email — submissions land directly in the engineering triage queue and replies come back in the same panel.

Submitting

1. Settings → Feedback / Bug report.
2. Type into the text box. Markdown is supported (code blocks, lists, headings).
3. Hit Submit. Your submission appears in the History list immediately.

A submission carries:

• The text you wrote.
• Your tenant ID + user email (so we can reach you).
• The Pentestas build version + commit hash at submit time.
• The browser + platform string.

It does not carry scan content, findings, or credentials. If you want us to look at a specific scan, paste the scan ID into the message and we'll request access through the normal tenant-scoped flow.

What gets attached automatically

Nothing beyond the metadata above. We do not auto-attach screenshots, scan logs, or session state. If you want us to see a screenshot, paste it into the message body (Markdown image syntax with a public URL works; a description in plain text works equally well for triage).

History and replies

The History list on the same page shows:

• Your past submissions with their text and date.
• Pentestas staff replies inline beneath each entry.
• Status: open, in-progress, closed.

Tenant admins see every submission from members of their tenant; regular users see only their own.

Admin view

In the Admin panel (superadmin only), the Feedback tab lists every submission across every tenant, with the same metadata, plus controls to:

• Reply (visible to the submitter).
• Mark in-progress / closed.
• Delete (use sparingly — only for spam or duplicates).

Where the data is stored

feedback_requests table in the platform database. Encrypted at rest like every other tenant-scoped table. Retention: kept indefinitely unless explicitly deleted by an admin.

When to use feedback vs. email

See also

• Troubleshooting — common issues that may not need a bug report
• Validation — how the Accuracy Gate filters findings before you see them