The current Documents Hub includes tags and nested folders for basic organization. Higher role levels can expose saved views, classification rules, and organization schedules. Administrators have additional controls for smart collections, webhooks, and administrative document operations. These are permission tiers, not separate copies of the document library.

Saved views apply filters to documents the current user is allowed to access. Smart collections evaluate configured conditions against eligible documents; they do not copy files or expand access. Classification rules and schedules run through authorized background work and remain subject to the same tenant and document checks.

Where enabled, document sharing grants specific access or creates a revocable, expiring share link. Comments, mentions, version comparison, and restore actions are permission checked. Restoring a prior version creates a controlled document state; review the result before relying on it.

Shared Qel Connect documents remain ordinary source files processed by the Documents Hub. Qel Connect membership controls access to the shared item; it does not make the document zero-knowledge or remove server-side processing needed for preview, OCR, and indexing.

Eligible users can select multiple documents for supported actions such as organization or processing recovery. The API checks each item independently and can return a mix of accepted and rejected results. Quarantine is a security state: inspect the displayed reason and use the offered release or removal action only when authorized. Destructive actions require confirmation where the interface provides it.

The backend is authoritative for role permissions and tenant access. The public guide intentionally describes capability classes rather than promising that every account can see every control. Webhook delivery, schedules, scanning, and document processing also require their corresponding backend workers and configuration.

For the implementation-level route map and current feature matrix, see the repository's Documents Hub user guide. Verify its commit-specific deployment notes before treating them as rollout evidence.