Back to Top

What to Expect When Working in SharePoint

SharePoint does not behave like a traditional file system. This page explains why files, access, syncing, and collaboration may feel different, and how to understand what is happening.

Why this page exists

SharePoint does not behave like a traditional file system.

Most “issues” are not system problems. They are the result of how files are stored, shared, synced, and accessed.

This page explains what you are seeing and why it happens.

Files behave differently in SharePoint

In SharePoint:

  • Files are shared, not copied
  • Access is controlled separately from visibility
  • The same file may appear in more than one place
  • Your local copy is not always the source

Key idea: If something feels different, it may not be broken. It may simply be working differently from a traditional shared drive.

You can see a file but cannot use it

Seeing a file does not always mean you have permission to open, edit, or share it.

You may be able to:

  • See it in search
  • Receive a link to it
  • View its name in a library

But still not be able to open or edit it.

What you can seeWhat it does not always mean
A file name in searchThat you can open or edit it
A shared linkThat the link matches your access
A file in a libraryThat you can change it

Key idea: Access is intentional, not automatic.

Files may feel locked or unavailable

Sometimes a file behaves like only one person can edit it.

This may happen because:

  • Someone is actively working on the file
  • The file did not close properly
  • The library is using an older setting called check-out

Important: Modern SharePoint is designed for real-time collaboration.

If only one person can edit a file at a time, the site may be using a legacy check-out setting.

Check-out is an older SharePoint feature that:

  • Prevents multiple people from editing at the same time
  • Requires people to manually check files in
  • Can block normal real-time collaboration

Key idea: SharePoint is designed for shared editing, not file locking. If check-out is enabled, contact the site owner to review whether that setting is still needed.

There may be multiple versions of the same file

If you see files named things like final_v2, final_v3, or final_final, that is usually not a system issue.

It usually means files were copied instead of shared or edited in place.

What happenedWhy it causes confusion
A file was copiedEach copy becomes a separate file
Different people edited different copiesNo one knows which file is current
Attachments were emailed back and forthThere is no single source of truth

Key idea: SharePoint is built for one file, not many copies. Use version history instead of manually creating new versions.

You may not find files where you expect them

Finding a file in SharePoint is often about understanding context.

Instead of searching randomly, ask:

  • Who owns the file?
  • Which team or project would store it?
  • Was it shared in Teams?
  • Was it shared in a chat or by email?

Key idea: Finding files in SharePoint is about understanding where the work belongs.

Files do not always live where you think they do

Teams is often where people work, but it is not where files are stored.

Where the file was sharedWhere it is stored
Teams channelSharePoint
Teams chatOneDrive
OneDriveOneDrive
SharePoint siteSharePoint

Key idea: Teams is not storage. It is an interface for collaboration.

Files may appear to disappear

If a file is missing, it may have been moved, deleted, renamed, or stored somewhere else.

Before assuming it is gone, check:

  1. Search
  2. Recent files
  3. The related SharePoint site
  4. Recycle Bin
Recovery stageWhat it means
First-stage Recycle BinItems can usually be restored by people with appropriate access
Second-stage Recycle BinFinal recovery stage, usually handled by site owners or administrators

Important: Deleted files are not kept forever. If something is missing, act as soon as possible.

Your computer may not match SharePoint immediately

If files look different on your computer than they do online, it may be related to sync.

This can happen when:

  • Sync has not completed
  • You worked offline
  • A conflict was created
  • You are looking at a copied file instead of the source file

Key idea: Your device is not the source. SharePoint is.

What you seeWhat it may mean
File is available locallyA copy has been synced to your device
File is online-onlyIt appears locally but opens from SharePoint when needed
File has a conflict nameChanges were made in more than one place

What actually causes most SharePoint problems

Most SharePoint problems are caused by how content is managed, not by SharePoint itself.

PatternWhy it causes problems
Copying instead of sharingCreates multiple versions of the same file
Storing files in the wrong placeMakes files harder to find and manage
Overcomplicating foldersMakes navigation and search harder
Creating unnecessary permissionsMakes access difficult to understand and troubleshoot
Unclear ownershipNo one knows who should approve access or maintain content

How to think when something feels wrong

Instead of asking “What is wrong with SharePoint?”, ask:

  • Who owns this file?
  • Where should it live?
  • How was it shared?
  • Am I working on the right version?

When to ask for help

Sometimes the issue is not just behavior or configuration.

Ask for help when:

  • Files cannot be recovered
  • Access is clearly incorrect
  • Sync repeatedly fails
  • Multiple people are affected

Need help?

If you are unsure what is happening, start with VITA for guidance or contact the IT Service Desk.