Set Item-Level Permissions in a SharePoint List: Practical Checklist for SharePoint Owners

As a SharePoint site owner, you may need to restrict access to specific rows within a list without changing the entire list or site permissions. This is common for HR records, project tasks, or confidential data where each item belongs to a different team or individual. Item-level permissions let you break inheritance on a single list item and assign unique permissions to that item alone. This article explains the prerequisite conditions, provides a step-by-step checklist for setting item-level permissions, and highlights common pitfalls that can break your list later.

What Are Item-Level Permissions in SharePoint Lists?

Item-level permissions allow you to override the default list permissions for a single list item. By default, every item in a SharePoint list inherits permissions from the list itself. When you break that inheritance, the item becomes a separate securable object. You can then grant or deny permissions to individual users or Microsoft 365 groups for that item only.

This feature is essential for lists that contain sensitive data such as employee reviews, vendor contracts, or confidential project tasks. Without item-level permissions, any user who can view the list can see every item in it. With item-level permissions, you can hide an item from everyone except a small set of people.

There are two important prerequisites before you begin. First, you must have at least Full Control or Design permission level on the list. Second, the list must not be in a view that forces read access on all items — if the list settings enforce read access for all users, item-level permissions cannot restrict visibility.

Checklist: Set Item-Level Permissions on a SharePoint List Item

1. Open the SharePoint list and locate the target item
   Go to your SharePoint site, open the list that contains the item you want to restrict. Navigate to the item by browsing the list view or using the search box.
2. Open the item details and access the permissions page
   Click the item title or select the item row, then click the ellipsis (three dots) and choose Manage access. Alternatively, from the item details page, click the ellipsis menu and select Manage access.
3. Stop inheriting permissions from the list
   In the Manage access panel, click the Advanced permissions settings link at the bottom. This opens the Permissions page for that item. Click Stop Inheriting Permissions in the ribbon. A confirmation dialog appears — click OK.
4. Remove all default permission groups
   After breaking inheritance, the item still shows all the list-level groups (for example, Members, Visitors, Owners). Select each group by checking the box next to its name, then click Remove User Permissions in the ribbon. Confirm each removal. Do not remove the system account or the site collection administrator unless you intend to deny access to everyone.
5. Grant permissions to the specific users or groups
   Click Grant Permissions in the ribbon. In the Share dialog, type the names or email addresses of the users or Microsoft 365 groups who should have access. Choose a permission level — typically Contribute for editing or Read for view-only. Click Share.
6. Verify the permissions are applied correctly
   Sign out of SharePoint or open a private browser window. Log in as one of the users you granted access to. Navigate to the list and confirm they can see only the items they have permission to. For users without explicit permission, the item should not appear in any list view.

Common Mistakes and Limitations of Item-Level Permissions

Users can still see the item in search results

Item-level permissions do not automatically hide the item from SharePoint search. If search indexing is enabled, the item content may appear in search results even if a user does not have direct list access. To prevent this, you must configure the item to be excluded from search or set the list to No Index in search settings.

Item-level permissions break list views and workflows

When you break inheritance on many items, list views may show inconsistent results. A user with permissions on some items will see those items but not others, which can confuse users who expect to see all items in a view. Power Automate flows that modify items may fail if the flow owner does not have permissions on every item the flow touches.

Copying or moving an item resets permissions

If you copy or move an item to another list or library, the item-level permissions are lost. The copied item inherits permissions from the destination list. Always reapply item-level permissions after moving items.

Performance issues with hundreds of unique permission items

SharePoint has a soft limit of 50,000 unique permission scopes per site collection. Each item with broken inheritance counts as one scope. If your list has more than a few hundred items with unique permissions, you may experience slow load times or timeout errors. Use item-level permissions sparingly and only for items that truly need restricted access.

Item-Level Permissions vs List-Level Permissions: Key Differences

Item	Item-Level Permissions	List-Level Permissions
Scope of effect	Single list item	Entire list and all items in it
Setup complexity	Must break inheritance on each item individually	Set once in list settings
Performance impact	High when applied to hundreds of items	Minimal
Search visibility	Item may still appear in search	List permissions control search visibility
Workflow compatibility	Flows may fail on items without owner permissions	Flows run under the list owner context

Item-level permissions give you fine-grained control over sensitive data in SharePoint lists. Use the checklist above to apply them correctly and avoid the common mistakes that can lead to broken views, failed workflows, or performance problems. For lists with more than 50 items that need unique permissions, consider creating separate lists for each audience instead of using item-level permissions at scale.