You can gate the whole app or just selected features behind a purchase. First set up your products and plans in Selling your app, then tell the builder exactly which people should have access.
Whole-app visibility and feature paywalls
Purchase Required is a whole-app access setting. A feature paywall is custom app behavior, such as allowing free users to view a dashboard while reserving exports for subscribers. Changing a button or hiding a page is not enough to protect the underlying data or server action.
The current standard app template sends signed-out visitors to /login. For Purchase Required, a signed-in person without an active or trialing entitlement is sent to /purchase. That route does not by itself select a product or prove checkout is configured. The app's purchase page still needs the correct plan links.
Older or customized apps can behave differently. Test the actual app, including your admin account: an admin role does not automatically bypass purchase checks.
Test before customers use it
Check the live app with a signed-out browser, an unpaid account and a buyer account. Also check the account you use to administer the app. Verify both the screen and the protected action; a visible button is not proof of permission.
Use the editor's test checkout flow where available. Do not make a real purchase just to discover what an access rule does.
Give someone complimentary access
When Comp a user is available under Monetize, choose the app's plan and enter the person's email. The tool creates a single-redemption, 100%-off code scoped to that plan. Share it privately; the person applies it at the app's checkout to claim the order. Creating the code alone is not an access grant.
The discount is limited-duration; it does not make a recurring plan free forever. Confirm the displayed discount and renewal terms before the person completes checkout. A code is also not a way to cancel charges on an existing subscription.
For permanent staff access, have the builder inspect the app's access rules and add an explicitly authorized staff path if needed. Check both page access and server-side permissions. Do not replace purchase verification with a browser-only flag or give every signed-in user access.
An unlisted link is not an identity check: anyone who obtains it can open it. Use actual account permissions for private staff access.
Trials and cancellation
A trial must be configured on the plan and reflected in the app's entitlement checks. Do not promise an automatic trial-ending email without confirming the payment provider's actual notification settings. If you build your own reminder, first confirm that the integration supplies a trial-end timestamp—the current standard entitlement payload does not supply a usable one automatically. Handle cancellation and duplicate sends; do not guess the date from signup time.
Check the subscription's actual cancellation and access-end status before telling a buyer when access stops. See Refunds and cancellations.