# Shared it view-only, they can still edit: fixing the default link

> View-only SharePoint or OneDrive link, but people can still edit? Check the default link permission, then site groups, then Manage Access, in that order.

[( Insights)](https://tenantcraft.ca/insights)

You picked Can view, and the person still edited the file. The link is rarely the whole story. A sharing link only adds access, so edit rights coming from a site group or an old Edit link stay put. Here is the order to check, and how to fix the right layer.

Stage

Govern

Topic

SharePoint

Published

Oct 26, 2026

Written by

[Geri Crroj](https://tenantcraft.ca/about)

Tested in a live tenant, October 26, 2026

(Short version)

A view-only link never removes access someone already has. Check three places in order: the default link permission in the SharePoint admin center, the site's groups (Members get Edit by default), and Manage Access on the file. Fix the layer that is actually granting edit, then have the person try again.

**Applies to:** SharePoint Online, OneDrive for work or school

One day I noticed something odd in a document library. A staff member I had given read access showed up as the last person to modify a document.

My first thought was that I’d shared it wrong. So I shared it again, and took screenshots this time. His permission said Viewer. He could still edit.

The same complaint turns up on admin discussion boards. Someone shares a Word file as view-only. Then the recipient’s name shows “Editing” next to it. The admin is sure they picked Can view, and they did. The link was set correctly. It just wasn’t the only thing giving that person access.

The 5-minute version

1.  **A view-only link never takes access away.** If someone can already edit through a group, the link doesn’t change that.
2.  **Check the default link permission first.** In the SharePoint admin center it can be set to Edit, so every link starts as an edit link unless the sharer changes it.
3.  **Then check the site’s groups.** Members get Edit by default, and on a Public team site that can mean every employee.
4.  **Open Manage Access on the file.** People, Groups and Links show every route in. Clicking a name shows that person’s full access.
5.  **Fix the layer that grants edit, then retest.** Changing the link does nothing if the edit comes from a group.

## The real cause: access adds up

A sharing link adds one more route to a file. It doesn’t replace the routes a person already has.

In SharePoint, a person can reach a file in several ways at once:

-   **A site group,** like Owners, Members or Visitors.
-   **A direct grant** on the file, folder or library.
-   **One or more sharing links,** each with its own View or Edit setting.

SharePoint adds the routes together, and the person gets everything they allow. If any one of them says Edit, they can edit.

So when someone says “I shared it view-only and they can still edit,” it usually comes down to this:

1.  The link was actually created as an edit link, because that was the default.
2.  The person is in a site group that has Edit.
3.  Somebody shared it with them earlier, with Edit, and that link or grant is still there.

Check them in that order. The first takes a minute and affects every file in the tenant. The other two are about this one file.

## Step 1: Check the default link permission

Start in the **SharePoint admin center**. Expand **Policies** and select **Sharing**, then scroll to **File and folder links**.

There are two settings here. The first picks the link type that’s selected by default. The second picks the permission that’s selected by default for sharing links: **View** or **Edit**.

![The File and folder links section of the SharePoint admin center Sharing page. The default link type is set to Anyone with the link. Under the permission that's selected by default, View is clear and Edit is selected and ringed.](https://tenantcraft.ca/images/vo-01-default-link-edit.png)

Admin center > Policies > Sharing

The test tenant for this post, before any changes. Every new link starts as an edit link. The sharer has to remember to switch it to View each time.

If it says **Edit**, every person in your organization who clicks Share starts with an edit link. They can change it to Can view, but the choice is easy to miss.

In the test tenant for this post, it was set to **Edit**, with **Anyone with the link** as the default type. That’s the most open combination there is.

Set it to **View** and select **Save**. People can still choose Edit when they need it. They just have to choose it on purpose.

This setting only changes what’s preselected when someone creates a link. A link that was already sent keeps the permission it was made with. So if the problem file was shared last month as an edit link, Step 3 is where you’ll find it.

### One site can override the tenant

Each site can have its own default. Per [Microsoft’s steps for a single site](https://learn.microsoft.com/en-us/sharepoint/change-default-sharing-link), go to **Active sites**, select the site, and select **Sharing**. Under **Default link permission**, a checkbox reads **Same as organization-level setting**. If it’s cleared, that site uses its own default, and it may still be Edit.

Check this for the site where the problem file lives.

## Step 2: Check whether a site group grants edit

Now go to the site itself. Open **Settings** (the gear), then **Site permissions**. At the bottom of that panel, select **Advanced permissions settings**. That opens the classic Permissions page.

![The classic Permissions page for a SharePoint site. The ribbon's Check Permissions button is ringed. Below it, three SharePoint groups are listed: IntraTeam Members with Edit, IntraTeam Owners with Full Control, and IntraTeam Visitors with Read.](https://tenantcraft.ca/images/vo-02-site-permissions.png)

Site permissions > Advanced permissions settings

The three default groups. Anyone in Members can edit every file that inherits from the site, whatever link they were sent.

Look at the **Permission Levels** column. By default, [Microsoft gives the Members group Edit](https://learn.microsoft.com/en-us/sharepoint/default-sharepoint-groups), Owners get Full Control, and Visitors get Read.

So if your “viewer” is in Members, they can edit, and the view-only link you sent them made no difference.

To check one person, select **Check Permissions** on the ribbon. Type their name and select **Check Now**. The result shows their permission level and where it comes from.

### The Public team site trap

There’s one group that catches people out: **Everyone except external users.** Every person in your organization is in it.

Microsoft’s docs say that when a team site connected to a Microsoft 365 group is set to Public, that group gets **Edit** by default. That means every employee can edit every file on that site. A view-only link to one of those files changes nothing.

If the problem site is a Public team site, that’s probably your answer.

## Step 3: Open Manage Access on the file

Steps 1 and 2 cover the tenant and the site. This step covers the one file. It’s where you see every route in, side by side.

In the library, select the file. Select **Details** on the command bar, then **Manage access** in the pane that opens. You can also get there from **Share**, through the circles in the bottom left of the share window.

The panel sorts access into tabs:

-   **People:** everyone with direct access, and their permission.
-   **Groups:** the site groups that reach this file.
-   **Links:** every sharing link made for it, and what each one allows.

![The Manage Access panel for a file, with the Groups tab open. IntraTeam Owners shows Owner, IntraTeam Visitors shows Can view, and IntraTeam Members shows Can edit. The Members row is ringed.](https://tenantcraft.ca/images/vo-03-manage-access-groups.png)

Library > file > Details > Manage access > Groups

This file had never been shared. Anyone in Members could already edit it, through the site group.

Now go back to **People** and select the person’s name. Microsoft calls the panel that opens the **Access summary**. [Per Microsoft’s guide](https://support.microsoft.com/en-us/sharepoint/sharepoint-sharing-and-permissions/see-who-a-file-is-shared-with-in-onedrive-or-sharepoint), it includes the groups that have access to the site, not just links. So it shows every route that person has, in one place.

Then check the **Links** tab. Look for an older link set to edit. One forwarded edit link is enough.

## Step 4: Fix the layer that grants edit

Once you know where the edit comes from, the fix is short. Change the wrong layer and nothing happens.

| What you found | The fix |
| --- | --- |
| The link was created as Edit | Delete that link in the **Links** tab. Share again with **Can view**. Set the tenant default to **View**. |
| An old edit link is still active | Delete it in the **Links** tab. Anyone who opened it loses that route. |
| The person is in **Members** | Move them to **Visitors** if they should only read the whole site. |
| They need Edit on the site, but not this file | Give the file or folder its own permissions and set that person to Read there. |
| **Everyone except external users** has Edit | Make the team site Private, or move sensitive files to a site with tighter groups. |
| A direct grant says Edit | Change it to **Can view** in the **People** tab. |

About giving a file its own permissions: it works, but each one is a small exception someone has to remember. Do it for a folder, not for dozens of single files. My [post on broken permission inheritance](https://tenantcraft.ca/insights/find-broken-permission-inheritance) shows how fast those exceptions pile up.

If whole groups of people are in the wrong group, fix the site layout, not the file. [This permissions layout for one site](https://tenantcraft.ca/insights/sharepoint-permissions-layout-one-site) is a good place to start.

## Step 5: Have them try again

Don’t take the panel’s word for it. Ask the person to close the file, reopen it in Word for the web, and try to type.

When they can’t, the fix held. If they still can, go back to Manage Access and select their name again. There’s a route you missed. Usually it’s a second group, or a link someone forwarded to them.

## What this does not fix

Setting the default to View makes the safe choice the easy one. It doesn’t stop anyone from picking Edit, and it has other limits too.

-   **People can still choose Edit.** The default only sets what’s preselected. Anyone allowed to share can switch the link to Can edit.
-   **Older Office apps ignore it.** Microsoft says the default link setting doesn’t affect Outlook Web App, Outlook 2016, or Office clients prior to Office 2016.
-   **View still allows download.** Someone with Can view can usually download a copy and edit it on their own computer. Your file in SharePoint doesn’t change, but you have no control over that copy.
-   **It doesn’t touch links already sent.** Every old edit link keeps working until you delete it or it expires.

If a file truly must not change, sharing settings aren’t enough on their own. Use a site where only a few named people are in Members, and block download on the link where the option is offered.

## The bottom line

A view-only link adds a view-only route. It never removes an edit route that’s already there.

When someone edits a file you shared as view-only, check in order. First the default link permission in the admin center. Then the site’s groups. Then Manage Access on the file. Fix the layer that grants edit, and have the person try again.

If you’d like someone to walk your sites and find where edit is coming from, that’s a focused job for an [hour bank](https://tenantcraft.ca/services/hourly).

Edit access hiding in site groups is the first thing a permissions cleanup finds. The prep guide shows you where to look.

Permissions Cleanup & Governance Prep Checklist

PDF · 7 pages · 45 checkpoints

[Email me the PDF](https://tenantcraft.ca/resources/guides/permissions-cleanup-prep)

---

_Canonical HTML: https://tenantcraft.ca/insights/sharepoint-view-only-link-still-editing · Agent guide: https://tenantcraft.ca/llms.txt · Site map: https://tenantcraft.ca/sitemap-index.xml_
