# Share a spreadsheet without it getting misaligned: why 'protecting cells' isn't security and what to do instead

> Protecting cells in Excel or Google Sheets prevents editing, not viewing. What each option really prevents, the 4 typical wrecks, and how to grant permissions by table, view, and field with BaseTable.

- **Source (source):** https://aistohire.com/basetable-flexible-online-database-154/blog/share-spreadsheet-without-it-getting-misaligned
- **Platform (platform):** AIstoHire
- **Language (language):** en
- **Updated (updated):** 2026-11-20

## In summary

- **Protecting a sheet in Excel or locking a range in Google Sheets prevents editing, it does not prevent viewing.** Microsoft and Google literally state this in their own support documentation.
- **Hiding a tab does not hide anything**: anyone with edit permission can show it again in two clicks.
- **The workaround of `IMPORTRANGE` creates a copy and a permanent authorization between files** that remains active even if you delete the formula.
- The only structural solution is **not to send the data that person should not see to the browser**: permissions by table, by view, and by field, applied on the server.
- **BaseTable**, the database app from **AIsToHire**, does exactly that: for each person and table, you choose *No access*, *Reader*, or *Editor*, mark which views they see, and, field by field, whether they can *Edit*, *View only*, or leave it *Hidden*.

---

There comes a moment in the life of every shared spreadsheet when someone asks: "Can’t I share it but only let them see their part?" The honest answer, in Excel and Google Sheets, is not entirely. This article explains why —with Microsoft and Google documentation in hand— what each option they offer truly prevents, and how it is resolved when you put permissions on the data instead of on the rectangle of cells. The practical example is set up with [BaseTable, the flexible database from AIsToHire](/basetable-flexible-online-database-154), which allows you to decide access field by field.

It is not a problem of bad faith from anyone. It is that a spreadsheet is designed for anyone to write anything in any cell, and everything that has been added on top —locks, protections, hidden tabs— are layers of convenience, not access control.

![Three people in front of a screen with a grid of data: each one is illuminated by light only in a different strip of the table](https://cdn.aistohire.com/i/9212-szmn-jdqv-uofy-wkln.webp)

## "Protecting cells" controls who edits, not who sees

Protecting a sheet or a range prevents someone from **modifying** those cells, but does not prevent them from **seeing** them: they are still there, on screen, ready to be copied. Microsoft and Google do not hide this; they state it in their own help. If your goal is for a person not to know a piece of data, cell protection is not the tool.

> "Spreadsheet-level protection is not intended as a security feature."
> — Microsoft, *Protect a spreadsheet*, `support.microsoft.com` (accessed on October 25, 2026)

> "However, this does not serve as a security measure, as users will be able to print, copy, paste, and export copies of a protected spreadsheet."
> — Google, *Protect, hide, and edit sheets*, `support.google.com/docs/answer/1218656` (accessed on October 25, 2026)

The same Google help page is equally clear about hidden tabs: **"Any of the editors will be able to show and see those sheets."** Hiding a sheet is a gesture of visual order, not a lock.

## What each spreadsheet option truly prevents

This is the table that is good to have in front of you before promising anyone that "they will only see their own." None of the six options prevents a piece of data from being accessible to anyone who opens the file.

| What you do | What it truly prevents | What it DOES NOT prevent | How anyone bypasses it |
|---|---|---|---|
| Lock cells + Protect sheet (Excel) | Writing in the locked cells | Seeing them, copying them, printing them | Copy and paste into a new file |
| Protect a range with "Restrict who can edit" (Sheets) | Editing that range | Viewing and exporting it | File → Make a copy |
| Hide a tab | Nothing: it's cosmetic | Showing it again | View → Hidden sheets |
| Share the file as *Reader* | Changing any data | Viewing **the entire** file | Not necessary: they already see it all |
| Copy the data to another file with `IMPORTRANGE` | Touching the original file | The copy becoming outdated or expanding | Editing the range of the formula and bringing in other tabs |
| Send a PDF or a screenshot | Editing anything | The data being frozen and needing to be redone each time | — |

![Comparison: on the left, a whole visible table with a lock over two rows; on the right, the same table with three columns that simply are not there](https://cdn.aistohire.com/i/0043-biqv-apiz-xpxa-izlq.webp)

The case of `IMPORTRANGE` deserves a separate warning because it is the most recommended workaround in forums and ages the worst. The authorization is granted **only once between the two files** and remains active even if you delete the formula: the link is not revoked automatically. And anyone with edit permission on the destination file can change the range of that formula and bring in other tabs from the source, even if they have no permissions on the source.

## The four typical wrecks of a shared sheet

Accidents in a shared sheet are almost never malicious: they are four normal gestures that a spreadsheet allows because a cell has no type or owner. These are the four, with the exact mechanism by which they break the calculations.

1. **Pasting with Ctrl+V over a column of formulas.** Pasting replaces the formula with a fixed value. The column continues to show a nice-looking number, but it has stopped calculating. It is usually discovered at the month-end close, when it is no longer known since when.
2. **Sorting a single column instead of the entire range.** The rows become misaligned: the amount of one row ends up next to the name of another. Since there is no primary key that ties the row in a sheet, there is no automatic way to detect or undo it once saved.
3. **Inserting or deleting rows in between.** Named ranges, the `SUMIF` pointing to `A2:A500`, and validation rules shift or fall short. The total still gives a number; it simply stops including the last rows.
4. **Manually writing the status.** `Pending`, `pending`, and `Pending ` (with a space at the end) are three distinct values for a filter and for a `COUNTIF`. The counts stop matching without anything seeming broken.

All four have the same origin: the sheet accepts any content in any position. A column of type *Single selection* with closed options, or a column of type *Date*, make cases 1 and 4 impossible by design.

## The alternative is to set permissions on the data, not on the rectangle

In a database, permissions do not hang from a range of cells, but from the structure: the table, the view, and the field. And what matters is not where the lock is drawn, but **where it is applied**: if the filter happens on the server, the data that that person cannot see never even reaches their browser, so there is no copy, no export, and no browser inspector that can pull it out.

![Diagram of four stacked glass layers: filtering from all the cells of the base to a few, and in the final layer each cell appears lit, dimmed, or off](https://cdn.aistohire.com/i/6313-fahe-cndn-licj-ubzo.webp)

In BaseTable, that control has four levels, and all four are configured from the same screen:

| Level | What you decide in it | Real options |
|---|---|---|
| **Base** | Whether the person enters or not | Shared / not shared |
| **Table** | What they can do within each table | *No access* · *Reader* · *Editor* |
| **View** | What cuts of that table they see | All, or only the views you mark |
| **Field** | Column by column, what they see and what they touch | *According to role* · *Edit* · *View only* · *Hidden* |

Three details worth knowing before setting it up, as they condition the design:

- **A field marked *Hidden* does not travel.** The server removes it from the response before sending it, both when opening the base and when loading the table or requesting a single record. It is not a `display:none` on the screen.
- **The primary field can never be hidden.** It is the name by which each record is identified; without it, the person would see anonymous rows. The app prevents it when saving.
- **The structure is closed for those receiving access.** A guest can create, edit, move, duplicate, delete, and restore **records**, and comment. They cannot create, rename, or delete bases, tables, fields, or views, nor change who the base is shared with. That barrier is on the server, not just on the buttons.

## How to set it up, step by step, with a real case

The typical case: a small agency with a base of four tables —*Clients*, *Projects*, *Tasks*, and *Suppliers*— that incorporates a freelance designer. She needs to see and update her tasks, check which project each one belongs to, and **not** see rates, margins, or client contacts. There are seven steps, and they are done only once.

![Process in three steps: first the person's profile with her email, then a matrix of switches turned on, dimmed, and off, and finally a link with a key that passes from one hand to another](https://cdn.aistohire.com/i/2947-dywf-jjhz-uzzr-zokg.webp)

1. **Add her to the directory.** On the home screen, gear → *Options* → *Users* → name and email. The directory is unique for your entire workspace (up to 100 people) and is reused across all bases: the profile is created once, not one per base.
2. **Open *Share* in the base.** From the base card menu on the home screen, or from the *Share* button on the top bar with the base open. Add the person from the directory.
3. **Set the role table by table.** *Tasks* → **Editor**. *Projects* → **Viewer**. *Clients* and *Suppliers* → **No access**. The tables in *No access* disappear for her: they do not appear in the tab list.
4. **Enter *Views and fields* of the Tasks table.** In *Visible views*, check only the view that corresponds to her —for example, a kanban already filtered by responsible person— and leave the rest out. If you don’t check any, she sees all.
5. **Adjust *Field permissions*.** `Status` → *Edit*. `Hours` → *Edit*. `Project` → *View only*. `Rate/hour` → *Hidden*. `Internal notes` → *Hidden*. What you leave in *According to role* inherits the role of the table (editor edits, viewer only sees).
6. **Decide if she can adjust the filters.** The checkbox *"Can adjust views locally (filter, sort, group…)"* controls whether that person can reorganize the view for herself. Uncheck it if you want her to see exactly the cut you prepared.
7. **Click *Generate invitation link*** and send it to her via the channel you use.

About that link, there are three rules to avoid surprises:

- **It is for one-time use** and only works if the person registers or logs in with **the same email** that you put in her directory profile. If it doesn’t match, the invitation is rejected.
- **Regenerating it invalidates the previous one**, whether someone has used it or not. If the link has gone where it shouldn’t, regenerating it kills it.
- **Removing someone from the directory revokes access from all bases at once**, and also cancels her invitation and link. It is the button for "this person no longer works here".

## What BaseTable does not do: the limitations, clearly

An access control is of little use if you don’t know where it ends. This is what you **will not** find, said before you discover it halfway through the migration:

- **There is no real-time editing.** You will not see the cursors of other people. If two people touch the same record at the same time, the fields combine and the last writing of each field wins. This matters for teams that edit the same cell simultaneously all day.
- **Anyone receiving access needs an account.** There are no public links for "view without registering" or public forms for outsiders. The *Form* view exists and is very useful —it creates records by filling in only the fields you choose, with required fields and help texts— but it is used **within** the app, by someone who already has access.
- **The view settings of an invitee are not saved.** If they filter, sort, or hide columns in a shared base, it applies to that session. Saved views belong to the owner of the base.
- **Formulas are calculated in the browser.** If a formula, a *lookup*, or a *rollup* uses a field that is *Hidden* for that person, that value will appear empty for her. It’s advisable to check this by entering as a guest before considering the configuration good.
- **There are numerical limits.** Per workspace: 20 bases, 20 tables per base, 60 fields and 60 views per table, 5,000 records per table, 100 people in the directory, 100 options per selection field, 30 attachments per cell, and 15 MB per file.
- **This is application access control, not end-to-end encryption.** It protects who sees what within the app; it does not replace your organization’s security policy. For a password or an API key, the *Vault* field stores a link to the AIsToHire Vault app instead of leaving the secret written in a cell of the table.

## What you do gain: a trace of who changed what

What a shared spreadsheet never gives you is the account of what happened. Here, each record carries its own history, and that changes conversations from "this was wrong" to "this was changed on Tuesday".

- **Field history per record:** creation, update (with the previous and new value of each field), deletion and restoration, with who and when. The trace is preserved even for records that have already been deleted.
- **Comments per record**, up to 2,000 characters each, with pagination. Each person can delete their own and no one deletes others'.
- **Undo and redo** with `Ctrl+Z` and `Ctrl+Y` (or `Ctrl+Shift+Z`), with a stack of 50 steps covering cell edits, creations, deletions, and row movements.
- **Restore deleted items**: a deleted record is recreated with its values. Watch out for one detail: it is recreated with a new identifier, so links pointing to it from other tables are not automatically rebuilt.

## Checklist before sharing a database

Seven one-minute checks that prevent 90% of the scares:

1. Is there any field with an amount, a margin, a cost, or personal data that this person shouldn't see? Mark it **Hidden**, not *View only*.
2. Does the primary field of each shared table reveal anything sensitive by itself? It can't be hidden: if the name of the record is already the problem, change which field is primary.
3. Are the untouched tables set to **No access**, and not to *Reader*?
4. Is there any visible formula that calculates from a hidden field? Check what that person really sees.
5. Are the marked views filtered as you expect? A view without a filter shows the entire table.
6. Is the email of the directory record exactly what that person will use to log in?
7. Will you need to revoke access someday? Note that this is done by removing the person from the directory, not base by base.

## Frequently Asked Questions

### Can I hide a column from a specific person in Excel or Google Sheets?

No, not reliably. You can visually hide the column and you can protect the range so they can't edit it, but anyone with access to the file can show it again, copy the content, or export it. Google's own help warns that protection "is not a security measure." The only real way is for the data not to be in the file that person opens.

### What if I password-protect the Excel sheet?

Password protection of a sheet prevents editing of locked cells, but Microsoft states bluntly in its documentation: "worksheet protection is not intended as a security feature." It does not encrypt the content or prevent it from being viewed. Encrypting the **entire file** with a password protects the whole file, but then they either see everything or see nothing.

### How do I make each salesperson see only their clients?

In a spreadsheet, by duplicating the file for each salesperson or setting up a filtered `IMPORTRANGE`, at the cost of maintenance and the risks that entails. In BaseTable, this is done with a view filtered by responsible person, marking it as the only visible view for that person and keeping sensitive fields *Hidden*. The filtering of fields occurs on the server, so the data from others is not even downloaded in their browser.

### Can I give access to someone who doesn't have an account?

They will need to create one, and also with the same email you have put in their directory record: the invitation link checks that match, and if it doesn't fit, they cannot enter. There is no "view without registering" or public read-only links.

### What happens when someone leaves the team?

You remove them from the people directory and they lose access to all databases at once, their invitation is canceled, and their link is severed. You don't have to go base by base. The records they created and their comments remain where they are, with their authorship in the history.

### Can I transfer my current spreadsheet without retyping everything?

Yes. You can import a CSV per table, with a preview before confirming and automatic detection of the type of each column (text, number, checkbox, date, URL, including the decimal comma). If you're coming from Airtable, there is an importer that brings entire bases with their tables, fields, views, attachments, and collaborators. And any view can be exported to CSV whenever you want to take the data.

### Can two people write at the same time on the same record?

They can, but you won't see their cursor live. Changes are combined field by field and, if both touch **the same** field almost at the same time, the last write prevails. If your team needs simultaneous co-editing like a shared document, this is not the tool.

### How much does it cost to get started?

You can create your account and your first database for free from the browser, without installing anything. The current plans and limits can be checked within the platform itself.

---

**BaseTable is the AIsToHire app that turns a spreadsheet into a database with real permissions: share each base by giving each person a role per table, the views you choose, and field-by-field permissions (*Edit*, *View only*, or *Hidden*), with the filtering applied on the server.** It's available at [BaseTable — Flexible spreadsheet-style database](/basetable-flexible-online-database-154) and is used from the browser.

> Set up your first database in BaseTable with the tables you already have —import a CSV or bring your Airtable bases—, share one of them with someone on your team, and hide the two fields that should never leave home. Creating an account is free and can be done from your browser.

- [BaseTable — Flexible spreadsheet-style database](https://aistohire.com/basetable-flexible-online-database-154)

## About the platform

**BaseTable — Flexible spreadsheet-style database** — an app by AIstoHire. Available at: https://aistohire.com/basetable-flexible-online-database-154/blog/share-spreadsheet-without-it-getting-misaligned

### Other languages

- `es`: https://aistohire.com/es/basetable-base-datos-flexible-online-154/blog/compartir-hoja-de-calculo-sin-que-la-descuadren
- `fr`: https://aistohire.com/fr/basetable-base-de-donnees-flexible-en-ligne-154/blog/partager-feuille-de-calcul-sans-qu-elle-soit-deformee
- `it`: https://aistohire.com/it/basetable-database-flessibile-online-154/blog/condividere-foglio-di-calcolo-senza-che-venga-scombussolato
- `pt`: https://aistohire.com/pt/basetable-banco-de-dados-flexivel-online-154/blog/compartilhar-planilha-sem-que-a-desconfigure
- `de`: https://aistohire.com/de/basetable-flexible-online-datenbank-154/blog/eine-tabelle-teilen-ohne-dass-sie-durcheinandergeraten
- `bg`: https://aistohire.com/bg/basetable-onlayn-baza-danni-kato-elektronna-tablitsa-bez-programirane-154/blog/sporedelyane-na-elektronna-tablitsa-bez-da-ya-razmestyat
- `ja`: https://aistohire.com/ja/nokodo-database-spreadsheet-154/blog/supureddoshito-kyoyu-hogo-kengen-taisaku
- `nl`: https://aistohire.com/nl/basetable-online-database-als-spreadsheet-zonder-code-154/blog/spreadsheet-delen-zonder-dat-ze-hem-verknoeien
- `ko`: https://aistohire.com/ko/basetable-nocode-database-spreadsheet-154/blog/spreadsheet-gongyu-gwollan-seoljeong
- `sv`: https://aistohire.com/sv/basetable-databas-online-i-kalkylbladsstil-utan-kod-154/blog/dela-kalkylblad-utan-att-nagon-stor-det
- `da`: https://aistohire.com/da/basetable-online-database-som-et-regneark-uden-kode-154/blog/dele-regneark-uden-at-det-bliver-rodet-til
- `ar`: https://aistohire.com/ar/basetable-qaada-bianat-aunlain-shbiha-bjdul-albianat-dun-brmja-154/blog/musharakat-jadwal-bayanat-bidun-ikhtilal
- `no`: https://aistohire.com/no/basetable-database-pa-nett-i-regnearkstil-uten-koding-154/blog/dele-regneark-uten-at-noen-odelegger-det
- `fi`: https://aistohire.com/fi/basetable-taulukkolaskennan-kaltainen-tietokanta-netissa-ilman-koodausta-154/blog/taulukon-jakaminen-ilman-etta-menee-sekaisin
- `zh`: https://aistohire.com/zh/basetable-no-code-spreadsheet-database-154/blog/gongyong-shisuanbiao-baohu-chucunge-quanxian
- `pl`: https://aistohire.com/pl/basetable-baza-danych-online-jak-arkusz-bez-programowania-154/blog/udostepnianie-arkusza-kalkulacyjnego-bez-balaganu
- `he`: https://aistohire.com/he/basetable-msd-ntonim-aonliin-bsgnon-gilion-bli-tknot-154/blog/shituf-gilayon-elektroni-bli-shyishbru-oto
- `cs`: https://aistohire.com/cs/basetable-online-databaze-ve-stylu-tabulky-bez-programovani-154/blog/jak-sdilet-tabulku-bez-rozbiti-ochrana-bunek
- `id`: https://aistohire.com/id/basetable-basis-data-online-seperti-lembar-kerja-tanpa-coding-154/blog/membagikan-lembar-kerja-tanpa-dikacaukan
