Never lose an edit to a teammate again.

It collaborates the same way Smartsheet does, with a save-based model rather than live keystroke sync. Your edits stage locally and flush when you hit Save, and a WebSocket pushes a "Jane saved changes to this sheet" banner to everyone else viewing it. There is no character-by-character cursor following and no CRDT layer, because for a spreadsheet that is overkill. What we added on top is conflict safety, so two people saving the same row never silently overwrite each other.

Every row carries a version number. When you save, your request includes the version you started from. If someone saved first, the server returns a 409 conflict with their current row instead of clobbering it, and you get a side-by-side diff of your value next to theirs on the exact cell that collided. You then choose Keep mine, Use theirs, or merge cell by cell. Rows you did not touch save normally with no prompt.

Three roles: viewer, editor, and admin. Viewers can read, editors can change cells and rows, and admins can also manage who else has access. The same three roles apply at every level, whether you grant access on a whole project, a folder, or a single sheet.

Inheritance is additive and flows downward. A grant on a project applies to its folders and sheets, and a grant on a folder applies to the sheets inside it. When you have access through more than one path, the highest role wins. Wisegrid resolves your effective role by walking from the sheet up through its folder chain to the project and taking the strongest grant it finds.

Yes. You can invite a person by email at a chosen role, and the invite stays valid for 14 days. They accept and create an account to join. If you just need someone to look without signing in at all, you can instead create a public read-only share link to the sheet.

Yes. An editor or admin on the sheet can mint a tokenized read-only link that opens without logging in. You can set an expiry date, protect it with a password, and revoke it at any time. The link is best-effort obscurity rather than a hard security boundary on its own, which is why password protection is there for anything sensitive.

Yes. You can create a view-only public link to one row (a wisegrid.co/r/ address), with the same optional password and expiry controls as a full sheet link. It is handy for sending one record to an outside contact without exposing the rest of the sheet.

No. Anyone you send a public share link to can view without an account, so they never consume a seat. Beyond that, view-only collaborators you add are always free and are never auto-converted into a paid seat just because they open a sheet. You only pay for editor seats: adding someone who can edit is a deliberate $19 per month seat, with every feature included and no Enterprise upsell.

Both. Comments anchor to a row by default, and you can also pin a comment to a specific cell within that row. Threads stay on the row, so a reply hangs off the original comment rather than spanning rows. Adding comments needs editor access to the sheet.

Not yet. Comments and threaded replies ship today, but @mentions and the notifications that go with them are still on the roadmap rather than live. We would rather say that plainly than imply a feature that is not there.

Yes. Files attach directly to a row and are stored on Cloudflare R2, so they live with the record instead of in a separate chat. There is no per-file cap, bounded only by your account storage (100 GB). The uploader or a sheet editor can delete an attachment.

Yes. Every row change, column edit, and share is written to an activity log with the actor, the before-and-after diff, and a timestamp, and it is queryable per sheet. That is also how the live change banner and the conflict diff know what moved.