Plans and Entitlements

Last verified: 2026-07-08

Awthy should explain plan boundaries in plain language. A locked feature should tell the site owner what is locked and why without showing provider credentials, export controls, or partial workflows they cannot use.

Core protection

Core login-security features include administrator/staff authenticator setup, recovery readiness, passkeys where allowed, login challenge protection, brute-force slowing, and safe recovery paths.

Paid convenience and operations

Paid entitlements can unlock broader customer convenience, trusted-device policy, advanced support evidence, audit-log visibility, export destinations, managed reporting, IP access rules, incident response, notifications/webhooks, and agency operations.

The exact active boundary is the site's current license state. The plugin UI should be treated as the source of truth for what the connected install can use.

Do not overpromise

Do not market parked future plans as available features. Avoid claims such as fraud scoring, chargeback protection, bank reconciliation, accounting automation, compliance certification, malware cleanup, or session replay unless a shipped feature and reviewed docs support that exact claim.

Upgrade prompts

Upgrade prompts should preserve security context. They may explain the operational value of the paid feature, but they should not expose sensitive rows, setup fields, provider credentials, or export job controls before entitlement is active.

Trials and previews

Preview or trial language must make the boundary clear. A feature can be visible for planning, connection repair, or safe preview while still keeping locked actions unavailable until entitlement is active.