RPost's implementation typically involves a straightforward setup process that can be completed in a matter of minutes to a few hours, depending on the integration level.
RPost, through its RMail service, is designed for ease of deployment across various platforms like Microsoft Outlook, Gmail, Salesforce, and secure email gateways. Here's a breakdown of the typical implementation process and timeline:
For enterprise setups, RPost offers secure email gateway integration and API access for automation.
Enable features like Registered Receipt™, SMART encryption, and AI-infused data leak prevention.
Users are guided through features like secure file sharing, certified proof of delivery, and targeted attack alerts.
Once verified, rollout to users or departments.
RMail is designed to integrate seamlessly into existing email platforms (Outlook, Gmail, Salesforce, etc.) and offers several layers of customization depending on the subscription tier:
Custom Branding: Optional white-labeling for client-facing communications.
Supports Apps for enhanced functionality across platforms.
Offers plugins and drivers for Windows and Outlook to convert files to RPD (Registered PDF) format.
RPost provides a variety of resources to help new users get started and stay productive:
RPost implements rigorous technical and organizational safeguards to ensure data privacy and integrity:
RPost emphasizes user control and privacy across its services (RMail, RSign, RDocs):
RMail users can retrieve Registered Receipt™ records and encrypted messages.
Retention Policies: Envelope data (e.g., signed documents) is retained for a configurable period—typically up to 90 days—after which it may be purged unless archived by the user.
RPost’s licensing and provisioning model supports dynamic scaling: