Back to Top

Who Owns What in SharePoint

Learn who is responsible for SharePoint sites, libraries, files, lists, access, and content quality, and what each role needs to manage over time.

Everything in SharePoint has an owner

In SharePoint, nothing should be treated as ownerless.

This includes:

  • Sites
  • Document libraries
  • Folders
  • Files
  • Lists

Ownership matters because it determines:

  • Who controls access
  • Who maintains structure
  • Who keeps content accurate
  • Who decides how information is organized

Simple rule: If no one owns it, it will not be maintained.

Roles and responsibilities

Several roles may be involved in managing SharePoint content. Each role has a different responsibility.

RoleMain responsibilitySimple way to think about it
KAUST ITProvides and supports the SharePoint platform.Platform provider
Site OwnerManages the overall site, access, structure, and ownership.Site accountable owner
Content OwnerMaintains specific files, pages, folders, lists, or content areas.Content responsible person
Data StewardDefines how data should be understood, used, and maintained.Meaning and quality
Data CustodianHelps ensure data is stored, protected, and handled appropriately.Storage and protection
SharePoint LibrarianMaintains the site’s structure, content quality, permissions discipline, and agreed ways of working.Site caretaker

What KAUST IT does

KAUST IT provides the SharePoint platform and supports its use across the KAUST community.

KAUST IT is responsible for:

  • Providing SharePoint as a service
  • Supporting platform availability and performance
  • Managing infrastructure and platform-level security controls
  • Supporting Microsoft 365 integration
  • Providing guidance, training, and technical support

KAUST IT is not responsible for:

  • Organizing your files
  • Deciding who should access your site or content
  • Cleaning up outdated or duplicate files
  • Maintaining your libraries, lists, metadata, or pages
  • Deciding how your team should structure its work

Key idea: KAUST IT provides the platform. Teams decide how to use it and are responsible for managing their content.

Site Owner

The Site Owner is responsible for the overall SharePoint site.

Site Owners are responsible for:

  • Site structure and layout
  • Who has access to the site
  • Managing permissions at a high level
  • Ensuring the site supports the team’s needs
  • Removing or updating access when people move or leave

Best practice: Every site should have at least one clear Site Owner. Ideally, there should be two or more to avoid ownership gaps.

Content Owner

A Content Owner is responsible for specific content within a site. This may include files, pages, folders, libraries, lists, or other content areas.

Content Owners are responsible for:

  • Keeping content accurate and up to date
  • Sharing content appropriately
  • Removing outdated or duplicate files
  • Ensuring files are stored in the correct location
  • Confirming content is still needed over time

Important: Creating or uploading content means taking responsibility for keeping it useful, accurate, and properly stored.

Data Steward and Data Custodian

Some SharePoint sites or libraries may contain structured, sensitive, operational, or business-critical data. In these cases, Data Steward and Data Custodian responsibilities are important.

RoleFocusResponsible for
Data StewardMeaning, quality, and use of dataDefining how data should be used, ensuring accuracy, and setting expectations for maintenance.
Data CustodianStorage, protection, and handling of dataEnsuring data is stored correctly, protected appropriately, and handled according to relevant requirements.

Simple distinction: The Data Steward focuses on what the data means and how it should be used. The Data Custodian focuses on how the data is stored and protected.

The SharePoint Librarian

The SharePoint Librarian is not a Microsoft-defined role. It is a recommended role used in KAUST IT Training Academy guidance to help teams keep their SharePoint sites organized and useful over time.

A SharePoint Librarian actively helps manage:

  • Site structure
  • Libraries and folders
  • Metadata and views
  • Pages and content
  • Lists and list data
  • Permissions and access exceptions

The SharePoint Librarian helps ensure:

  • Naming conventions are followed
  • Files are saved in the right place
  • Lists remain accurate and up to date
  • Custom permissions are tracked and reviewed
  • The site continues to meet the team’s needs

Key idea: SharePoint works best when someone is actively maintaining it.

How teams should agree to use SharePoint

SharePoint is not self-organizing. It works best when teams agree on how they will use it.

Teams should align on:

  • Naming conventions
  • Where files should be saved
  • How long content should be kept
  • What belongs in the SharePoint site
  • How libraries and lists should be maintained
  • How permissions should be managed

Important: These are team decisions, not IT decisions. KAUST IT provides the platform, but each team is responsible for using it in a way that supports their work.

When people move teams or leave KAUST

People often move internally at KAUST or leave a team. When this happens, shared content and access must be reviewed.

Before someone leaves a team, they should:

  • Move shared content from OneDrive to the team SharePoint site
  • Ensure the team has access to files needed for ongoing work
  • Transfer ownership where needed
  • Confirm that important content is not left in a personal location

Site Owners should:

  • Remove or update access for the person leaving
  • Reassign site, library, or content ownership as needed
  • Review permissions and group memberships
  • Confirm that shared work remains available to the team

Important: If team content remains in a personal OneDrive, it may become inaccessible, unmanaged, or lost when roles change.

Managing permissions responsibly

Permissions should be simple, clear, and easy to understand.

Recommended approach

  • Keep permissions at the site or library level where possible
  • Use groups instead of assigning access to individuals one by one
  • Track custom permissions when they are necessary
  • Review access regularly

Avoid

  • Too many unique permission exceptions
  • Assigning access individually when a group would work better
  • Creating restricted areas without documenting them
  • Leaving former team members with access they no longer need

Best practices

Do

  • Assign clear owners for sites, libraries, and important content
  • Use SharePoint for team-owned content
  • Agree on naming conventions and structure
  • Keep lists, libraries, and pages up to date
  • Review ownership and permissions regularly

Avoid

  • Treating SharePoint as a dumping ground
  • Leaving content in personal OneDrive when it belongs to the team
  • Assuming IT manages your files and structure
  • Letting custom permissions grow without tracking them
  • Allowing content to become outdated or ownerless

What you should do

  • Know who owns the content you use
  • Store shared files in SharePoint, not OneDrive
  • Follow your team’s agreed structure and naming conventions
  • Take responsibility for content you create or manage
  • Review ownership and access when people move or leave

Need help?

If you are unsure who owns content or how to manage SharePoint responsibilities, start with VITA for guidance or contact the IT Service Desk.