Revver
Key Info:
Revver is a cloud document management and automation platform, formerly known as eFileCabinet. It combines structured document storage, search, permissions, version history, sharing, retention controls and configurable workflows intended to organise document-dependent work.
Details
Document organisation
Revver uses a cloud repository with folders, templates and structured document information to organise business content. Full-text search and previews help users retrieve and inspect files without moving through every folder. Version history preserves changes, and role-based permissions restrict access. Migration planning should map legacy folders, owners, duplicates and sensitive content before reproducing the old drive structure inside a new platform.
Automation around documents
Workflows can assign steps, approvals and actions around stored documents. Templates and repeatable folder structures support recurring client, employee or operational files, while reminders and status visibility reduce manual follow-up. The product also presents document sharing and electronic-signature-related processes. Buyers should test escalation, reassignment, rejected work, due dates and the audit evidence created when a workflow is changed after instances already exist.
Security and lifecycle
Permissions, version control, activity history and governance-oriented controls support protected document handling. Retention and disposition requirements should be mapped to actual rules rather than inferred from a general security claim. External sharing requires particular attention to expiry, recipient authentication, download controls and revocation. Confirm backup, recovery, export formats, ownership of encryption keys and the process for responding to an account or access review.
Fit and evaluation
Revver may suit small and midsize organisations or departmental teams that want cloud document management with workflow automation around repeatable records. The rebrand from eFileCabinet must be considered during migration, integration and user communication; this BBS card uses the current Revver identity. Test search, version recovery, permissions, a complete approval, a client share and a bulk export, including successfully revoked external access under load, then confirm API, identity, retention, support and plan-specific limits before rollout. Verify how former product names appear in imports and support records.
Decision record
Document the tested document types, retrieval results, permission model, exception handling, required edition or modules, migration assumptions and named operational owner. Keep unsupported pricing, customer-size, language and device values blank until a current official source maps them exactly to the BBS field.