Workspace access and roles
The server checks workspace membership and roles against the application database before allowing access.
Learn how YoMaily controls workspace access, protects provider credentials, and checks sending eligibility. Read the limits of those controls before connecting your services.
The server checks workspace membership and roles against the application database before allowing access.
Server authorization and PostgreSQL row-level security are separate checks against access to another workspace’s records.
Client provider credentials use encrypted storage scoped to the workspace. Diagnostic results redact secrets.
Human approval, suppressions, rate limits, quiet hours, and provider restrictions are checked before an eligible message is dispatched.
Service administration uses aggregate records and audited operational actions. It does not expose client campaign content or provider secrets.
Workspace plan limits apply to client capacity. Checks run on the server before additional capacity or sending is allowed.
Verified visitors can create an isolated workspace and select a plan through authenticated Stripe Checkout. Provider connections and campaign sending remain deliberate, workspace-specific actions: customers supply their own provider credentials, and sending requires setup, review, approval, and the applicable safety checks.
No public statement on this page is a certification, penetration-test report, availability SLA, or guarantee that an incident cannot occur.