Skip to content
Documentation Portal →

Using it

Not a product

This documents an internal test environment. See the overview for what POC Sandbox is and is not.

The sandbox exists to exercise the portal's paths. These are the ones worth running before you believe a change works.

File an issue

  1. Sign in to the portal
  2. New issue
  3. Choose any app — in POC mode they all route to the sandbox
  4. Write a title and a description, then submit

The issue appears in My issues immediately, and as a GitHub issue in the sandbox repo within a second or two.

Reply to an issue

Open the issue from My issues and use the reply box at the bottom. Your reply becomes a comment on the GitHub issue.

Replies from staff appear in the thread the same way, attributed to bydynamics Support rather than to a named person.

Internal notes are not shown

Staff can leave comments that customers never see. If you are testing as a customer and a comment is missing from the thread, check the issue on GitHub before assuming the thread is broken — it may be an internal note behaving exactly as intended.

Attach a file

Use Add a file on the issue. Attachments are stored separately from GitHub and served through the portal, so a file is only ever readable by someone who is signed in and entitled to that issue.

There are no download links in the issue body, and that is deliberate — a link that carries its own access token outlives every control around it once it is quoted into an email.

Check what a customer would see

The strongest sandbox test is the negative one: sign in as a different organisation and confirm the issue is not there.

An issue is visible only if both of these hold:

  • it was filed by the portal itself, and
  • it carries a customer: label your organisation is allowed to read

If either fails, the portal answers 404 — not 403. A "forbidden" would confirm the issue exists, which is enough to enumerate other customers' issue numbers one at a time.

What a correct failure looks like

Requesting another organisation's issue by number should give you the same response as requesting an issue number that was never created. If you can tell those two cases apart, that is a finding — report it.