How i setup a sharepoint list so that a user can only add new items and not see them afterwards ?

Hello Greg Booth

Thank you for raising this interesting question.

Your current setup is very close. The main challenge is that SharePoint does not natively support a true “add‑only, cannot see anything” experience when a list web part is present on a page. In practice, granting Add Items almost always implies View Items as well. Once users can see any list view, even an empty “Create Only” view, they can switch to All Items or other views and see their own records, due to the item‑level permissions you’ve configured.

Because of this, one possible improvement to your current approach would be to edit the custom page and remove the list web part entirely. Instead, you could add a simple button or link that directs users straight to the New Item form (NewForm.aspx), using a ?Source= parameter to redirect them back to your clean custom page after submission. This removes the ability to switch views, although it is still not 100% foolproof if users ever obtain the direct list URL.

A much cleaner and more robust option is to use the built‑in integrated form feature in Microsoft Lists / SharePoint lists. With this approach, users receive only a direct form link (or the form is embedded on a simple page or in a Teams tab). They can fill out and submit the form, and after submission they see only a confirmation or “Thank you” message, there is no list, no views, no items visible, and no way to navigate to the SharePoint list.

In this model, submitters do not need any permissions on the list itself, as the form securely handles submission. Items are still created with the correct Created By value, so your existing item‑level permissions (for example, “Read items that were created by the user”) continue to work exactly as expected for administrators or managers who do have list access. You can even remove list permissions from the CallHandlers group entirely if you wish, the form will still function correctly.

This approach completely eliminates the view‑switching issue you encountered with the list web part. It works well for internal users within your Microsoft 365 tenant, keeps the form separate from the list itself, and ensures users cannot see the list unless you explicitly grant them access. You may keep your AddOnly permission level if you still want certain users to have limited direct list access, but it is no longer required for form submitters.

Overall, this approach is simpler, more secure, and provides exactly the “add new items without seeing them afterward” behavior you are aiming for.

I hope this information is helpful.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Configure the list and its views/permissions so users can add items but never see any, including their own, by combining item-level permissions with a locked-down view configuration and custom permission level:

1. In the list’s Advanced settings (List settings → Advanced settings), set Item-level Permissions to the most restrictive options that still allow creation:
   • Read access: None (or, if not available in the UI, keep “Read items that were created by the user” but rely on view/permissions to block access).
   • Create and Edit access: Create items only (or “Create items and edit items that were created by the user” if that is the closest available option).
2. In List settings → Permissions for this list, ensure the list has unique permissions (no inheritance from the site) so that list-specific restrictions can be applied.
3. Use the custom AddOnly permission level at the site level, but remove all capabilities that allow users to see or manipulate list data beyond the form:
   • Include: Add Items only.
   • Remove: View Items, Edit Items, View Application Pages, Manage Personal Views, and any permission that allows browsing list data.
   • Assign this AddOnly permission level to the CallHandlers group on this list.
4. For views:
   • Keep a single default view that returns no items (for example, filter on ID = 0 so it always shows 0 records), as already configured.
   • Ensure users with AddOnly do not have permission to create, edit, or manage views. This is controlled by the permission level (remove Manage Personal Views and any list design permissions).
   • If necessary, break permission inheritance on the views or use a page that only exposes the NewForm.aspx (or a custom form) and does not show the list view web part at all.
5. Provide access to the list only through a page that hosts a New Item form (standard or custom). Do not place a list view web part on that page, or if a view web part is required, configure it to show no items and hide toolbar commands that allow switching views.

With this configuration, members of the CallHandlers group can open the “New Item” form and submit entries, but they cannot see any items in any view and cannot switch to “All Items” because their permission level does not allow viewing items or managing views.

References:

• Customize permissions for a SharePoint list or library
• Edit list settings
• Set custom permissions on a list by using the REST interface