Free CRUD Web App with Secret Key Login – Google Sheets

A CRUD dashboard with two locks on it. The password gets you as far as a second prompt; the secret key gets you in. It is a small idea that changes the threat model completely — a stolen password on its own opens nothing, because the key never leaves the account holder.

How the second gate behaves

Wrong credentials are refused outright with an invalid username or password message; the secret key prompt only appears once the password is correct, so an attacker guessing passwords learns nothing from the screen either way. Each user sets and changes their own key from inside the dashboard, exactly as they change their own password.

Records, and who sees them

The demo stores what the extra lock is there for: entries carrying a name, certificate, email address, password and the user they belong to — the kind of record you would otherwise keep in a notes app. An admin sees all of them; a user sees only the rows assigned to their own username. Add, edit and delete all work inline, with a confirmation before anything is removed, and a refresh button reloads the table straight from the sheet if a change has not appeared.

What you would use it for

Anything where the rows themselves are sensitive: credentials, licence keys, certificates, client account details. The same pattern also drops onto an ordinary CRUD app when you simply want a stronger login than one password.