Issue.coffeeSuite.coffee
Public channel and automation

Use public issue reporting and QR

Publish a focused form and let the reporter follow only their own issue.

1 min readUpdated Aug 23, 2026

Test a focused public reporting journey that verifies the reporter and exposes only one issue.

Before you start

  • Enable public reporting with active categories and locations.
  • Use an email able to receive the verification code.
Public Issue reporting form with category, location, problem details and reporter contact.
The public form creates a controlled report and verifies the exact request before submission.

Publish the controlled channel

Enable public reporting, choose active categories and locations and distribute the URL or generated QR. Public reports start open with source public.

Verify the reporter when required

Email verification uses a six-digit, time-limited, single-use code tied to the report data. The server validates it before creation.

Protect follow-up access

The reporter receives a random management token that shows only that issue and its public status. Internal comments, private evidence, team data and other issues are not exposed.

Step by step

  1. Open the public URL or QR.
  2. Choose category and location.
  3. Describe the observed problem and reporter details.
  4. Request and enter the six-digit code.
  5. Submit and test the private management link.

Final check

  • Only active resources are offered.
  • Verification is tied to the request.
  • The token exposes no internal comments or files.
Tip: Treat the public link as a reporting channel, not as authentication or a file-sharing URL.