The beta dashboard
Eleven pages: what changed since you last looked and what became of your reports, the programme, and a map of what the site exposes.
acada.ac/beta
Open itThe tester dashboard at acada.ac/beta has eleven pages. Start here is about you; the next six are the programme, and the last four map what the site exposes, for anyone looking for holes.
What's on it
| Page | What is on it |
|---|---|
| Start here | How many drops shipped since you last read What's new, what became of each report you sent, and where on the site you have filed from. |
| Getting in | Accounts and roles, test cards and other ways to pay, regional pricing and currency, and what needs one of us to act. |
| Feature tour | Every surface worth opening, by role. |
| Report a bug | Where a report goes, the template, the severity rubric, and what happens next. |
| Known issues | What we already know about, in the product and the security surface. If it is here, it needs no report unless you find it is worse. |
| What's new | One entry per drop, newest first. After a drop, retest what it names. |
| Rules & scope | What is fair game, what is not, and what we promise in return. |
| API inventory | Every route under /api, generated from the source. |
| Database surface | The functions you can call, the tables and their row-level security, the storage buckets and the scheduled jobs, read live. |
| Architecture | What runs where, and the rate limits. |
| Trust boundaries | Which role may reach which surface. |
Rules and limits
- A report shows as Not looked at yet, Being worked on, Fixed or Closed, with what we did once it is done. Only reports sent from the Feedback button appear.
- The count of new drops is kept in this browser.
- Read Known issues before you report, and What's new after each drop.
Checked against the app on 17 October 2026. If something here no longer matches what you see, say so below.
Related
Reporting a bug
Beta programme
What beta access includes
Beta programme
The beta rules
Beta programme
Was this article helpful?