ViewVault
Central control over SharePoint view sprawl. Lock down who can see, create, or modify list and library views — without stripping users of the permissions they need to do real work.
What ViewVault does
ViewVault gives site collection administrators centralized control over list and library view visibility, locking down who can see, create, or modify views across SharePoint without stripping users of the permissions they need to do their actual work. Standard views stay standard, executive dashboards stay intact, and end users stop tripping over each other's one-off filters.
Deployed as an SPFx web part scoped to the site collection level, ViewVault requires no tenant-wide footprint and no elevated admin roles beyond what you already manage. Site collection admins add the web part to an admin page, and every list and library in the collection becomes manageable from a single grid.
Behind the scenes, ViewVault respects SharePoint's existing permission model. There are no app-only tokens, no Graph scopes, and no data leaves your tenant. If you uninstall the web part, your views revert to standard SharePoint behavior with no residual configuration to clean up.
Key features
Built for admins who own the consequences of view drift across sprawling site collections.
Per-list view control
Every list and library in the site collection appears in one admin grid. Toggle visibility, creation, and modification independently for each.
Site collection scope
Scoped to the site collection level — no tenant-wide deployment, no cross-tenant footprint, no surprise reach beyond where you install it.
Respects existing permissions
Runs inside SharePoint's standard permission model. Users keep their existing rights to documents, items, and tasks — only view authoring is gated.
Lock executive dashboards
Standard views and exec-facing dashboards stay exactly how you built them. End users cannot accidentally re-filter, re-sort, or delete them.
MessageBar feedback
Inline MessageBar confirms every save and surfaces any error. Empty-state handling for lists with no custom views yet means no blank confusion.
Admin-only gating
Permission check hides the web part UI entirely from non-admins. The control surface never renders for users who cannot use it.
No elevated tenant role
No app-only tokens. No Graph scopes. No SharePoint admin role required beyond the site collection admin rights you already hold.
Watch the deck
A seven-slide walkthrough of the problem, the solution, and how ViewVault fits into your site collection.
Simple pricing
One annual licence per SharePoint tenant. All features included.
Annual
Per SharePoint tenant
- 15-day free trial
- All features included
- Email support
- All updates while subscribed
- Cancel any time
15-day free trial — no credit card required.
Contact us for volume or multi-tenant pricing — customersupport@dksolutions999.com.
Frequently asked questions
Does ViewVault work tenant-wide?
No — and that's intentional. ViewVault is scoped to the site collection level. You install the web part into a specific site collection and it controls views there. If you want to cover multiple site collections, you install it into each one. This keeps the blast radius small and the deployment story simple for admins who don't have tenant-wide reach.
Does it affect existing views?
No. ViewVault doesn't modify, delete, or rewrite any existing views. It controls visibility and authoring permissions on top of SharePoint's native view system. If you uninstall the web part, all your views revert to standard SharePoint behavior with no residual configuration left behind.
Can non-admins bypass it?
The ViewVault admin surface is gated behind a permission check and only renders for site collection administrators. Non-admins never see the control panel. The visibility and authoring rules you set are enforced inside SharePoint's permission model, not in client-side code alone, so end users cannot bypass them by opening a different browser or tab.
Does it integrate with Microsoft 365 groups?
ViewVault respects the existing SharePoint permission model, which already honours Microsoft 365 group membership. If a user is in a group that grants them site collection admin rights, they see the admin panel. If they're in a group with contribute rights, they're subject to whatever authoring rules you've configured. There's no separate group layer to manage — ViewVault simply reads what SharePoint already knows.