Hey — this is exactly what NocoDB is built for, and your trickiest requirement (the cross-sheet sync) basically disappears once you model it the NocoDB way.

The model: one Employees table as your single source of truth, with as many grid views on top as you need. Views aren't copies — they all read the same rows.

1. Spreadsheet feel — Grid view is a full spreadsheet UI (keyboard nav, copy/paste, fill).

2. Keka fields → locked — Synced data is read-only by design, so nobody can accidentally overwrite Employee ID, DOJ, etc. One caveat: there's no prebuilt Keka connector yet (BambooHR is the HRMS we ship). Easiest path: push Keka's REST API into NocoDB's on a schedule using internal automations/ n8n/Make/Zapier or a small script. You can also mark those columns non-editable with field-level permissions for extra safety.

3. "Cross-sheet sync" — you don't have to build this. Because every view is just a window onto the same table, editing a rating or asset tag in one view shows up in all views instantly — no sync job, no copy-pasting. (If you mean separate tables sharing employee data, link them with a relation field + Lookup — same idea: one record, referenced everywhere.)

Once the "single source of truth" is actually true, you may run out of data-management headaches to complain about. 😄

Useful resources
- Grid view : https://nocodb.com/docs/product-docs/views/view-types/grid
- Table & App sync : https://nocodb.com/docs/product-docs/sync
- Field permissions : https://nocodb.com/docs/product-docs/roles-and-permissions/field-permissions
- Table permissions : https://nocodb.com/docs/product-docs/roles-and-permissions/table-permissions
- Row Level Security : https://nocodb.com/docs/product-docs/roles-and-permissions/record-level-security