Mikesoft TeamVault

TeamVault is designed to keep files private by storing them outside the normal Media Library workflow and restricting access through authenticated WordPress workflows. Protection still depends on the server environment and the storage rules generated by the plugin.

No. TeamVault is designed for private operational documents that should stay separate from the public Media Library and normal website assets.

New activations grant the manage_private_documents capability to Administrators only. You can enable whitelist mode to limit workspace access to selected users. Sites upgraded from older releases should review existing role capabilities and whitelist settings if Editors previously had TeamVault access.

TeamVault is designed to avoid normal public Media Library URLs by routing access through authenticated WordPress workflows. The exact storage protection still depends on the server environment and the generated storage rules. Apache/LiteSpeed can enforce the generated .htaccess, IIS can enforce web.config, and Nginx requires an equivalent deny rule for /wp-content/uploads/private-documents/. For high-sensitivity deployments, use a custom storage path outside the public webroot.

Yes, if they have the required capability and, when whitelist mode is enabled, they are explicitly allowed in the plugin settings.

You can create TeamVault groups (independent from WordPress roles) and grant per-folder permissions to users or groups with granular actions: view, upload, download, delete, and manage. Child folders inherit the nearest parent's rules unless they define their own. A folder with no explicit rules keeps the default capability-based behavior, and administrators always retain full access. Granting view without download gives preview-only access, and ZIP export honors the same rule.

No. The governance features are opt-in. Folders without explicit permission rules behave exactly as before, and quotas, notifications, and white-label branding start disabled.

Yes. You can set per-user or per-group storage quotas. When an upload would exceed a limit it is blocked before anything is written, while existing files stay accessible. Administrators are never limited.

Yes. Groups, per-folder permissions, preview-only access, quotas, access reports with CSV export, email notifications, and white-label branding are all included for free in the core plugin.

The plugin supports a custom writable storage path at code/configuration level, but the standard admin workflow is built around the default private storage location.

The database records can remain visible even if the original binaries are missing. TeamVault includes cleanup and reindex maintenance tools for these recovery scenarios.

Yes. Inline PDF preview can be enabled or disabled in the settings.

The sidebar widget shows only the space used by TeamVault files. On many shared hosting platforms, PHP cannot reliably read the account quota shown by the hosting panel, so the plugin avoids showing misleading total or available values.

By default, TeamVault keeps its data for safety. You can enable full data removal before uninstall if you want the plugin to delete its files, folders, logs, and settings.