Permission & Access Issues

How to Restrict SharePoint List Views to Assigned Items Only

Aamir Naveed Akram Oct 8, 2026 869 views

Question details

The user needs to configure a SharePoint risk register so that departmental managers can only view their assigned risk items, while risk administrators maintain visibility of all items.

How to Restrict SharePoint List Views to Assigned Items

Product: SharePoint
Device & OS: not provided
Scenario: Configuring view restrictions and access permissions for a shared risk register list.
Observed behavior: By default, users can see all items in the list. The goal is to enforce strict visibility limits based on assigned items for regular managers while retaining full access for administrators.

Before you start

Ensure you have Site Owner or Full Control permissions on the SharePoint list before attempting to modify item-level access and break permission inheritance.

Solution 1Recommended

Configure Unique Item-Level Permissions Manually

Best for smaller lists. This method involves manually breaking permission inheritance for each risk item and assigning specific access.

To strictly prevent users from seeing items not assigned to them, you must use unique permissions rather than standard filtered views. Filtered views can be easily bypassed by users.

Open Manage Access

Navigate to your SharePoint list, select the specific risk item you want to restrict, and click the three dots (ellipsis) to select 'Manage access'.

Access Advanced Settings

In the Manage Access panel, click on 'Advanced settings' at the bottom to open the classic permissions management page.

Stop Inheriting Permissions

In the Permissions ribbon at the top, click 'Stop Inheriting Permissions' to break the link with the parent list's security settings.

Grant Specific Permissions

Remove any existing user groups that should not have access. Then, click 'Grant Permissions' in the ribbon to add the assigned departmental manager and give them 'Read' or 'Contribute' access.

Retain Administrator Access: When granting permissions, make sure to explicitly include your Risk Administrators group and assign them 'Full Control' so they do not lose visibility of the item.

Solution 2

Automate Permissions using Power Automate

Best for large lists (hundreds of items) where manual permission management is not feasible.

Free Microsoft Office alternative

Manage Data and Registers Easily with WPS Office

While SharePoint offers complex list management, WPS Office provides a lightweight, highly compatible alternative for managing tabular data. Use WPS Spreadsheet combined with WPS Cloud to easily maintain risk registers, protect specific cell ranges, and share files securely without complex network setups.

1. Download and Install: Download WPS Office Free and open WPS Spreadsheet to create your risk register.
2. Set Up Cell Protection: Organize your data and use the 'Protect Range' feature under the Review tab to lock specific sections.
3. Share Securely: Save the file to WPS Cloud and click 'Share' to generate secure links with specific view or edit permissions.

Highly compatible with Microsoft Excel (.xlsx) formats for seamless migration.Free and lightweight alternative to heavy enterprise deployment.Easily protect specific sheets or cell ranges for different managers.Built-in cloud collaboration with granular link-sharing view and edit permissions.

microsoft office alternative - wps office

Frequently Asked Questions

Can I restrict SharePoint list views without breaking permission inheritance?

Yes, you can create filtered views using the '[Me]' function (e.g., setting the filter to 'Assigned To' is equal to [Me]). However, this only hides the items from the default view; users can still access other items if they have a direct link or if they create their own custom views. For strict security, unique item-level permissions are required.

What happens if a SharePoint list has too many unique permissions?

SharePoint has a supported limit of 5,000 unique permissions per list. While it can technically hold more, exceeding this limit significantly degrades performance when loading list views and running queries. For massive registers, consider grouping items into folders and applying permissions at the folder level instead.

How do Risk Administrators retain access when inheritance is broken?

When breaking inheritance manually or via a Power Automate flow, the user performing the action usually retains access. However, to guarantee uninterrupted administrative access, you must explicitly add the Risk Administrators security group to the item's permissions and grant them 'Full Control'.

Document & File Issues