> ## Documentation Index
> Fetch the complete documentation index at: https://supastack.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For the full documentation corpus in one file, fetch: https://supastack.dev/llms-full.txt

# Mobile entitlements

Configure RevenueCat purchases and keep access decisions on the server.

## Understand the access status shown on your phone

An entitlement is permission to use a paid feature. It belongs to the active workspace, the group of account data your team uses. First complete native sign-in, then open the phone app's Settings → Billing. Read the displayed access status; loading or an error does not mean you have a subscription.

With purchases off, the app should not offer store checkout. To sell access, complete the RevenueCat purchase guide below and test in a native development build. After a test purchase, reopen Billing and confirm the server reports active access; after expiry, confirm the feature is locked again. If a purchase succeeds but access does not refresh, use Restore purchases and check the backend connection rather than buying a second time.

[Sign in from the native app](https://supastack.dev/docs/mobile/authentication.md)

[Configure store products and restore purchases](https://supastack.dev/docs/mobile/revenuecat.md)


## Read access from the server

The mobile entitlement client reads server-owned access state. Keep a loading or failed request distinct from an active subscription; the interface must not infer paid access because a request failed.

Use the presentation logic in apps/mobile/src/entitlements to translate that state into the native interface.


## Keep the purchase boundary explicit

Native purchases use RevenueCat when configured; web billing is a separate surface. Do not expose Stripe Checkout in the mobile interface or treat a store-side active flag as proof of server access.

The [In-app purchases guide](https://supastack.dev/docs/mobile/revenuecat.md) documents client keys, manager checks, workspace identity, purchase/restore sync, server verification, and sandbox setup. Real StoreKit or Play Billing acceptance requires an EAS development build; Submit to the app stores covers release.


## Check denied and expired access

Test unavailable, inactive, and active entitlement states, plus network failures. Verify that restricted actions remain unavailable when the server denies access, and that signing out clears the previous session’s presentation.


If you want to continue setup, read [Create mobile accounts](https://supastack.dev/docs/mobile/external-accounts.md).


## Next

[Create mobile accounts](https://supastack.dev/docs/mobile/external-accounts.md)