POC Sandbox¶
Not a product
POC Sandbox is an internal test environment for the bydynamics support platform. It is not on AppSource, it cannot be installed, and it is not licensed to anyone.
It is documented here for two reasons: the Portal lists it as a selectable app, so somebody will eventually click it and wonder what it is; and this section is the template every real app's documentation follows.
What it is¶
A throwaway GitHub repository — AL-SupportPortal-POC-Sandbox — that the Portal
can file issues into without any of them landing near a real customer.
When the portal is running in POC mode, every issue goes here regardless of which app was chosen on the form. That is the point: it lets the whole path be exercised end to end, from sign-in through to a filed issue and a reply, using data nobody has to be careful with.
Who uses it¶
| You are | What the sandbox is for you |
|---|---|
| A bydynamics engineer | Where you test a change to the portal before it touches a real repo |
| A customer | Nothing. You will never see it, and no issue you file reaches it |
The one rule¶
Synthetic data only
Never put real customer information into a sandbox issue — no company names, no ledger extracts, no screenshots of a live environment, no tenant IDs.
The sandbox is deliberately the least protected part of the platform. In POC mode the portal authenticates with a single shared key rather than per-person sign-in, which means everyone holding that key is indistinguishable in the audit trail. That is an acceptable trade for made-up data and an unacceptable one for anything else.
How to read the rest of this section¶
The four pages that follow are the shape every app's documentation takes:
- Setup — how to get it working, once
- Using it — the everyday tasks, in order
- Known issues — what is broken, and what to do instead
- Release notes — what changed, newest first
When the first real app is documented, copy this structure rather than inventing a new one. A customer who has read one app's docs should already know where to look in the next.