SharePoint
Team and organization content
SharePoint libraries are designed for shared business content, collaboration, permissions, and team ownership.
Everyday IT · SharePoint & OneDrive
Know whether the problem is access or sync.
SharePoint and OneDrive feel complicated because users experience the same files through several different paths.Browser access proves one thing. File Explorer sync proves another.
SharePoint vs OneDrive, plain English
Start by identifying who the files belong to and how they are being accessed.
OneDrive
An individual user's work storage
OneDrive is tied to a user's account and is best understood as that person's cloud file area, even though files can be shared with others.
Sync
A local view of cloud content
The OneDrive sync client can present SharePoint and OneDrive files in File Explorer. That local representation depends on the client, sign-in state, sync health, and local device.
Adding access the right way
Use the site's existing permission model rather than inventing a new one for each user.
01
Identify the correct site or library
Confirm exactly which SharePoint site, team, library, folder, or shared resource the user needs.
02
Compare with a working peer
Look at a user in the same role and determine whether access comes from a Microsoft 365 group, SharePoint group, security group, Teams membership, or another approved method.
03
Use group-based access where possible
Add the user to the existing role-based group instead of creating a one-off direct permission unless the business requirement truly calls for it.
04
Verify in the browser first
Before troubleshooting sync, prove the user can authenticate and open the required content directly in SharePoint or OneDrive on the web.
“It works in the browser but not File Explorer”
This is one of the most useful distinctions a new technician can learn.
Browser works
Cloud access is probably okay
If the user can open and edit the file in the browser, basic identity and SharePoint permission are likely working. Move your attention to the sync client and workstation.
Check sign-in
Is OneDrive using the right account?
Confirm the sync client is signed into the intended work account and not paused, disconnected, or prompting for credentials.
Check sync state
Read the OneDrive status
Look for sync errors, invalid file names, storage limits, conflicting changes, missing shortcuts, or a library that is no longer connected.
Then rebuild carefully
Do not unlink first and ask questions later
Before resetting, unlinking, or re-syncing a large library, understand what local files are pending and whether the user has unsynced changes.
Read the OneDrive status icons
The icon often tells you whether a file is cloud-only, cached locally, pinned, or still synchronizing.
Blue cloud
Cloud-only
The file is visible locally but uses minimal disk space until opened.
Green outlined check
Locally available
The file has a local copy and consumes disk space. It can usually be released with the supported Free up space action after sync health is confirmed.
Solid green circle
Always available on this device
The item is pinned locally and is intended to stay downloaded until that availability setting is changed.
Blue circular arrows
Synchronizing
Wait for active synchronization to finish before restarting, unlinking, or making broad availability changes.
Logical size and physical disk use are not the same thing.
A large OneDrive folder can include placeholders that do not consume the same amount of local storage. Compare Size with Size on disk and read the status icons before deleting anything.
Common access complaints
Translate the user's wording into a specific layer.
“I can see it but can't open it”
Check item-level or folder permissions
Visibility of a site or library does not guarantee permission to every folder or file. Check inheritance and the specific object's access.
“It worked yesterday”
Ask what changed
Look for group changes, account changes, sync client state, renamed or moved folders, expired sharing links, VPN/network changes, or a different signed-in account.
“The folder disappeared”
Separate cloud content from sync shortcuts
Verify the folder still exists online. A missing File Explorer entry may be a sync/shortcut problem rather than deleted data.
“My changes are missing”
Check where the file was edited
Confirm whether the user edited a synced copy, a local duplicate, an attachment, or the live SharePoint file before assuming data loss.
What not to touch casually
Large SharePoint and sync changes can create more confusion than the original ticket.
Red flag
Breaking permission inheritance
Unique permissions may be valid, but adding them casually makes future troubleshooting and audits harder.
Red flag
Mass moving or renaming
Large folder reorganizations can break shortcuts, links, user expectations, sync paths, and automations.
Red flag
Deleting local folders during sync troubleshooting
Make sure you know what is cloud-backed and what is local-only before removing or resetting data.
Red flag
Using broad Everyone access as a fix
Fix the intended permission path instead of bypassing the design with overly broad access.
Next Test
Separate cloud access from local sync state before resetting anything.
Browser works
File Explorer is stale or missing content
Keep the online library as the known-good source and isolate the account, sync relationship, client state, and local path before rebuilding anything. Diagnose browser versus local access
Scope differs
One user or device behaves differently
Compare one variable at a time before changing access or unlinking data. Use a known-good comparison
Reset proposed
Local and cloud data boundaries are unclear
Identify what can be lost, how to roll back, and how the original workflow will be verified. Plan the change safely
Case proof
Use the proof layer when permissions look correct but the SharePoint workflow still fails.
KT-000017
Authentication failed before authorization could complete
See how SharePoint permissions and their change result moved the investigation upstream to MFA state without treating reset as a generic first step. Read case KT-000017