CRUD Web App with Login & Activity Log – Google Apps Script

The CRUD app with a login in front of it and a memory behind it. Two roles decide who sees what, and every action taken is written to a history you can read afterwards.

Who sees which records

An admin opens the app and sees everything. A user opens it and sees only the records belonging to them. Nothing is hidden behind a filter they could clear — the data simply is not returned. And because the role comes from an access type column in the login sheet, promoting or demoting someone is changing one cell: the same username and password becomes an admin or a user depending on what that column says.

The history is the real upgrade

Every action is logged with who did it and when: admin logged in, user one added the record for employee 456, admin deleted the record for employee 1, admin logged out. When a record changes and nobody remembers changing it, this is the difference between an argument and an answer. A shared CRUD app without an audit trail becomes untrustworthy the first time something goes missing.

Everything from the base build

Full create, read, update and delete on records carrying ID, name, gender, address, email, phone, organisation and position — with up to five files uploaded per record into a Drive folder located by name, and their links written back to the sheet. The table stays usable on a narrow screen by collapsing overflow columns behind a row expander.

Staying signed in

Refreshing does not throw the user out; the session lasts until they press logout — which matters for a data-entry app someone has open all day.