In an equipment-planning web app, add a user-menu Privacy Mode that hides cost and customer data on the Sites, Deal Pipeline, Equipment and Allocation pages for screen sharing, as a remembered display preference that changes no permissions or saved values.
- Version
- Category
- Engineering
- Model configurations
- 1
- Attempts
- 8
- Public trials
- 162 passed
- Median runtime
- 24m 19s
Instruction
# Privacy Mode for screen sharing
Admins often share their screen in live demos of this workspace and need a
one-click way to keep cost and customer information off the screen while
they do.
Add **Privacy Mode**, switched on and off by an item named "Privacy Mode" in
the user menu (the account menu at the bottom of the sidebar). The item
shows whether Privacy Mode is currently on.
While Privacy Mode is on, the **Sites**, **Deal Pipeline**, **Equipment** and
**Allocation** pages show no cost or customer data. Which data that is
follows the app's existing column permissions: it is what the **Cost** and
**Tenant** column permissions protect, including the money amounts computed
from costs. For example, an admin on the Allocation page who expands rows
with committed equipment, or shows supply with Site-tagged on, sees no
customer in the source buckets listed there ("Customer - Site"). Everything
else on these pages — site, location and phase names, equipment, suppliers,
quantities and dates — stays visible, and switching Privacy Mode off shows
the hidden data again. Dialogs for creating or editing a record may still
show the values being edited.
Privacy Mode only changes what is displayed to the user who turned it on:
- It changes no one's permissions and none of the data the app stores.
- Editing, duplicating included, keeps working while it is on, and what is
saved keeps its real values, including any that are hidden at the time.
The choice is remembered: after a reload or a new page load in the same
browser, Privacy Mode is still on (or off), and a page loaded in Privacy
Mode never shows hidden data before hiding it.
## Environment
PostgreSQL on localhost:5432 and the local database endpoint the app's
driver uses are running when you start, and the dev env files point at the
dev database.
Public trials
Results by model
| Model · harness | Mean reward | Range | ± SE | Attempts |
|---|---|---|---|---|
| Frontier model ACursor CLI | 25.0% | 0% – 100% | 16.4 pp | 8 |