SharePoint Skills: Personal vs Site Scope
When you create a SharePoint component like a column, content type, or site page, you must choose between a personal scope (visible only to you) and a site scope (visible to everyone with access to that site). The correct choice depends on whether the item is for your own temporary use or for a shared team workflow, and picking wrong can cause confusion or broken permissions.
Background: Why Scope Exists
SharePoint has two main storage layers: the personal layer (part of OneDrive for Business and your personal “My Site”) and the site layer (a team site, communication site, or hub site). Every component you add—columns, content types, lists, pages, web parts—can exist in either layer. The personal layer is tied to your user profile and follows you across sites you visit, while the site layer is tied to a specific site URL and its permission groups.
Microsoft introduced personal scopes to let users customize their own experience without affecting the team. For example, you can create a personal view of a task list that filters out completed items, and no one else sees that view. Site scopes are for anything the team should share, like a “Customer Status” column that everyone uses in reports.
How Personal and Site Scope Work
When you add a column to a list or library, SharePoint asks whether it should be a “Column” (site level) or “List Column” (list level). Similarly, when you create a view, you choose “Public View” (site) or “Personal View” (personal). The scope determines where the definition is stored and who can see or edit it.
- Personal scope: Stored in your user profile’s personal site. Only you can see it, and it appears on any site you visit where the same list/library type exists. It does not affect other users.
- Site scope: Stored in the site’s content database. Available to all users with access to that site, and site owners can manage permissions on it. It appears only on that site (or sites that inherit from it).
For example, a personal view of a shared calendar can show only your own events, while a site view shows all team events. A site column can be added to multiple lists in the same site, but a personal column only exists in your own context.
How to Choose: Key Decision Factors
Use this checklist to decide quickly:
- Who needs it? If only you need the column/view/page, choose personal. If your team or department needs it, choose site.
- Is it temporary? Personal scope is ideal for one-off filters, sorting, or experimental columns you might delete later. Site scope is for permanent structures like a “Project Status” column used in reports.
- Do you need to share it? Site scope allows you to share with others via site permissions. Personal scope cannot be shared directly—you would have to recreate it for each user.
- Does it affect data? A site column can enforce data consistency (e.g., a choice column with predefined options). A personal column cannot enforce anything for the team.
- Where should it appear? Site scope appears on the site’s lists and libraries. Personal scope appears in your personal views but not in the site’s default views.
In practice, most team collaboration items should be site scope. Use personal scope for your own convenience, such as a personal view that filters out items you don’t care about.
Common Problems and Misconceptions
One frequent mistake is creating a personal view and then wondering why teammates can’t see it. Conversely, creating a site column that you only needed for one list can clutter the site’s column gallery and confuse others. Another issue is mixing scopes in the same list: if you have a personal view and a site view, they can show different data, leading to confusion about which is “correct.”
Misconception: “Personal scope is private.” That’s true for the definition, but the data it shows is still governed by list permissions. A personal view of a list still only shows items you have permission to see. Personal scope does not bypass security.
Also, personal scopes do not follow you across tenants. If you move to a different organization, your personal views and columns are not transferred.
Site vs Personal: Comparison Table
| Aspect | Personal Scope | Site Scope |
|---|---|---|
| Visibility | Only you | All site users |
| Storage location | Your OneDrive/My Site | Site content database |
| Sharing | Not shareable directly | Shareable via site permissions |
| Use case | Personal filters, temporary experiments | Team columns, content types, pages |
| Management | Only you can edit/delete | Site owners can edit/delete |
Cost and Administration Impact
There is no direct monetary cost difference between personal and site scope—both are included in your SharePoint license. However, there is an administrative cost: site scopes require governance. If every user creates site columns, the site can become cluttered, and site owners must spend time cleaning up. Personal scopes reduce that clutter but can lead to duplicated work if multiple users create the same personal views.
From a storage perspective, personal scopes consume storage in your personal site, which counts against your OneDrive quota. Site scopes consume site storage, which counts against the site collection quota. For most text-based components, the difference is negligible, but large custom scripts or images in personal scopes can add up.
Alternatives and Best Practices
If you need to share a view with a few people but not the whole site, consider creating a site view and then restricting access via a separate permission group. Alternatively, use a SharePoint “page” with a filtered web part that you can share with specific users. For columns, you can use a site column and add it to a specific list, rather than making it available site-wide.
Best practice: default to site scope for anything that others might need, and use personal scope only for your own temporary conveniences. Document your site’s column and view governance to avoid duplication. Regularly review personal scopes and delete ones you no longer use to keep your profile clean.
Frequently Asked Questions
Can I convert a personal view to a site view later?
Yes, but not automatically. You can create a new site view with the same settings, or save a personal view as a new view and then share it. However, any personal formatting or filters must be manually recreated.
Why can’t my team see the column I created?
Because you created it in personal scope. Check the column’s settings in the list; if it says “Personal,” recreate it as a site column or add it to the list as a site column.
Does personal scope affect performance?
No significant performance impact. Personal views are cached per user, while site views are cached per site. The main difference is storage and management overhead.
Can I use personal scope for a content type?
No. Content types are site-level or list-level only. Personal scope is only available for views and some web part settings, not for content types or site pages.
What happens to personal scopes when I leave the company?
Your personal site is deleted after the retention period, and all personal views and columns are removed. Site scopes remain and are unaffected.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.