A staff member loses access to a project folder. Someone shares the folder again to get them working. Months later, the project ends, but the extra access remains. Repeat that pattern across several teams and a SharePoint site becomes difficult to explain.
Cleaning up permissions begins with understanding who needs to do which work. A small business or nonprofit can make meaningful progress by reviewing one library, documenting the access people actually need, and testing changes before expanding the work.
This guide describes a practical cleanup process for an existing SharePoint Online environment. The examples are hypothetical. Use them to plan a review with your site owner and the people responsible for the documents.
For an introduction to groups and permission levels, start with SharePoint Permissions Explained for Small Businesses. This article focuses on planning and verifying a cleanup of access that has accumulated over time.
1. Define the business boundary before changing access
Choose a manageable area, such as a project library, a department site, or the collection of approved policies. Write down the business owner, the people who maintain the content, and the audience that uses it. Identify external partners separately because their relationship may end when a contract or project closes.
A useful scope statement could say, “Review the current project library, confirm staff and partner access, remove approved exceptions, and document the groups the project manager will maintain.” That gives the owner a decision to make and gives the reviewer a clear stopping point.
Record any material that requires a narrower audience, such as personnel records or restricted client information. Ask the owner whether the current location is appropriate. A folder called Confidential does not establish who should have access to its contents.
2. Understand inheritance and the different ways people get access
In SharePoint, files and folders normally inherit permissions from the location containing them. An item with unique permissions has its own permission scope. Sharing and administrative changes can create exceptions, which means neighboring documents may have different audiences. Microsoft describes these relationships in its permission guidance.
Microsoft guidance on permission scopes and inheritance
Also consider every source of a person's effective access. A person may receive permission through a group, a direct grant, a parent location, or a sharing link. Removing one grant can leave another route available. Microsoft's sharing guidance explains that people retain the highest permission available through their access sources.
Microsoft guidance on managing access and sharing links
For example, removing a contractor from a folder's direct-access list may leave them in a project group. The review needs to explain both routes. Asking whether they can still open the actual document is more informative than looking at a single entry in one dialog.
3. Make a small access register that supports decisions
For the area in scope, capture the site and library address, owner, expected audience, permission groups, direct grants, sharing links, and known exceptions. Include the date reviewed and the person responsible for the next decision. Store this register where authorized maintainers can find it.
Use a clear decision for each exception, such as retain, remove after approval, investigate, or relocate content. Include the reason. “External designer needs edit access until the campaign handoff” is more useful than “guest seems active.”
A hypothetical project review might produce these entries.
- Project Members group. Six current employees need editing rights. The project manager confirms the membership and becomes its maintenance owner.
- Former contractor. Direct access was added during a previous engagement. The project owner approves removal after checking that the handoff is complete.
- Leadership budget folder. Its audience differs from the rest of the project. The owner decides whether to keep a documented exception or move it into a more appropriate restricted location.
- Old sharing link. Nobody can identify a current purpose. Its owner investigates before the link is removed.
Keep the register focused on decisions and evidence. Avoid placing passwords, recovery codes, or sensitive document contents in an access inventory.
4. Design an access structure someone can maintain
Agree on recognizable groups and assign responsibility for membership. Where possible, let a shared audience inherit access from a clear boundary. An owner should be able to explain why the group exists, who approves additions, and when membership is reviewed.
Microsoft recommends built-in SharePoint groups for communication sites and the associated Microsoft 365 group for team-site membership. Site types and connected services matter, so confirm the site's relationship to Teams and Microsoft 365 before redesigning its access.
Microsoft guidance on groups and permission levels
Consider a separate library or site when a substantial collection has a different audience and owner. That is a design decision with consequences for links, navigation, search, and staff habits. A move should include a plan for people who rely on the current location.
Allow documented exceptions when the work requires them. Give each exception an owner and a review event, such as project closure or a partner contract renewal. This makes the next review a maintenance task instead of a new investigation.
5. Capture the starting position and approve the change
Before a cleanup, record the affected groups, membership, links, and permission assignments using a method suitable for the environment. For a small library, a carefully maintained register and administrator records may be sufficient. Larger sites may need a scoped report produced by someone who understands SharePoint permissions.
Confirm who can authorize removals and who can restore access if a business dependency was missed. Note the proposed change window, the users who will test, and the tasks that must continue working. A document copy alone does not capture the access configuration you need to reconstruct.
Review the impact of restoring inheritance especially carefully. The parent may have a broader audience than the restricted content should receive. Approve the target audience before applying a parent configuration to a child location.
6. Test required access and restricted access
Select representative accounts and ask their owners to perform agreed tasks. An administrator's own access gives an incomplete picture because administrative privileges may differ from a staff member's normal permissions.
- A reader can open the approved policy through the link staff normally use.
- A designated editor can update the working document in the correct library.
- An external partner can reach the agreed project content.
- A person outside the approved audience cannot open the restricted file.
- An expired collaboration link no longer grants access after its approved removal.
Record the account or role tested, the document address, the action, and the result. If the result is unexpected, investigate group membership and other access routes before making more changes. Staff should use their own accounts for testing and report results through the agreed support channel.
Also test important links from Teams tabs, intranet pages, and operating procedures. A technically correct permission change can still interrupt work if the team is directed to an obsolete location.
7. Finish with an operating routine
Hand the owner an updated register, the approved changes, test results, remaining decisions, and a short procedure for future requests. Explain where staff ask for access and who authorizes it. Connect this procedure to onboarding, role changes, and employee departures.
Schedule the next review around the work. A project site may need a review when the partner engagement ends. A department library may need membership checks when staff change roles. An exception without an owner or review point is likely to survive long after its purpose ends.
Track a few useful measures, such as unexplained grants still awaiting a decision, access requests resolved through approved groups, and recurring support problems. The goal is an access model the owner can describe and maintain.
When to bring in outside help
Professional help is useful when ownership is unclear, many items have different permissions, a proposed change affects several teams, or staff cannot identify how someone obtained access. Start with a limited review and an agreed outcome, then decide whether broader repair is justified.
J3 can help assess an existing site, organize access decisions, perform approved repairs, and document the handoff. Explore SharePoint intranet repair or a security and access review. If your next challenge is approved document ownership, read Which Version Is Approved?
Related reading
- How to Prevent Duplicate Tasks and Approvals in Power Automate
- Technology Change Management for Small Businesses: A Practical Checklist
Need help applying this?
Plan your SharePoint access cleanup.
Start with one site or library, agree on the access people need, and verify the repair.