Account access
Verified accounts, hashed passwords, optional authenticator MFA, device management, rotating credentials, and session invalidation protect account access.
Inspect the controls behind your mailbox connections, shared documents, signing links, team permissions, and AI access. Elite Mail Suite gives you clear ways to authorize, review, and revoke access.
Verified accounts, hashed passwords, optional authenticator MFA, device management, rotating credentials, and session invalidation protect account access.
Tenant-scoped APIs, exact-email invitations, and role-based team permissions keep workspace access tied to an authenticated account and approved role.
TLS in transit, rate limits, hardened non-root services, least-privilege service accounts, and security-focused response headers.
Database integrity monitoring, backup procedures, and recovery checks support dependable operation.
Security, administrative, and signature actions produce audit history so teams can review sensitive changes, access events, and completed signing records.
Standard tracking sends message metadata rather than message bodies. Provider refresh credentials are encrypted at rest; stored content and files enter through deliberate product workflows.
Reading, drafting, sending, and administration use distinct permissions. AI connections respect account and team policies, with review and confirmation for protected actions.
Opaque public tokens are hashed or encrypted according to the access workflow. Quarantined and revoked assets are denied before storage access.
Completed signature documents carry file hashes and completion records. Recipient-specific access and audit history preserve the context of the finished request.
Provider authorization shows the requested access. The connection supports the mailbox features you enable; standard tracking and stored campaign or document content have different data needs.
AI reading, drafting, and sending use separate permissions. Tracked AI messages and campaign launches require review of the prepared send. Configured workflows follow their authorization rules.
Owners and admins set role limits. A connection cannot grant more access than the user and team allow.
Review recent connection activity and workflow history. Check the action and its result before deciding what to do next.
Disconnect the provider or AI connection, pause the workflow, or revoke a document link. Revocation does not recall an already sent email or downloaded file.
The privacy policy and DPA explain retention and deletion, including different treatment of tracking metadata, uploaded content, and operational records.
Use the support contact and include enough detail to reproduce the issue. Do not access other users’ data, disrupt the service, or perform destructive testing. Credible reports are acknowledged and coordinated through remediation and disclosure.
Talk through workspace access, data handling, and deployment with us.