Using Entitlements as App Feature Flags
An entitlement describes what a user is allowed to use. While it is commonly tied to a subscription or one-time purchase, the same mechanism can control access to a beta feature, a single capability, or another gated area of an app without creating a new store product for that audience.
Why entitlements work as feature flags
Think of an entitlement as a named permission. Normally, buying a subscription product activates the linked entitlement for the subscription period, while a one-time purchase activates it indefinitely unless refunded. Because activation is separate from the store transaction itself, you can also activate the same entitlement manually for selected users. That separation is what makes it useful as a feature flag: the app checks a permission, and you decide remotely who receives it.
A four-step workflow
Create the entitlement first, then check it in the app, then decide how to grant it. A practical sequence is: 1) Add an entitlement in the app's entitlement settings with a clear identifier such as beta and a description of the gated capability. 2) Expect a warning if no product is attached; that only means purchases will not unlock it. 3) Check the entitlement through the SDK using the public contract module code0001, which reads the active status from CustomerInfo. 4) Grant access to selected users, either individually or at scale. 5) Re-check the SDK result for a granted user to confirm the flag is active before relying on it in production.
Choose the audience first
Start by deciding who belongs in the group. One concrete approach is to build a customer list filtered to long-standing paid subscribers who still have an active subscription, for example people who subscribed before 2020. In the worked example, that filter returned 33 users. You can open an individual profile from the list or export the list for later processing. The filter criteria are yours to choose; the key point is to define the audience before granting anything.
Grant access manually or at scale
For a handful of users, open the customer's history page, grant a promotional entitlement, choose the entitlement and how long access should last, then confirm. For a larger rollout, use the REST API to grant and revoke promotional entitlements programmatically; the exact request is held in protected module code0002. Requests that change entitlement access require a Secret API Key. Use the dashboard route for small, manual grants and the API route when you need repeatable, bulk changes.
Extend the pattern carefully
Once the flag is in place, you can extend the pattern beyond a beta group. Separate entitlements per feature give you finer control over who sees what, and make support and rollout decisions easier because each capability can be enabled or withdrawn independently. Before publishing, verify that a granted user reports the entitlement as active, a non-granted user does not, and revocation removes access as expected.
Frequently asked questions
Does the app need different code for purchased versus manually granted access?
No. The same active check works whether access came from a store purchase or a manual grant, because the SDK reports entitlement status in CustomerInfo without distinguishing the origin in that check.
Should I grant access one by one or programmatically?
For a small group, granting from the customer's history page in the dashboard is the simplest route. For larger groups, the REST API can grant and revoke promotional entitlements programmatically, using a Secret API Key for requests that modify access.
Why does an entitlement with no attached product show a warning?
A warning that no products are attached simply means store purchases will not unlock it. That is expected when access will be granted manually, so it can be ignored for this use case.
curl --request POST \
--url https:\/\/api.revenuecat.com\/v1\/subscribers\/app_user_id\/entitlements\/entitlement_identifier\/promotional \
--header 'Accept: application\/json' \
--header 'Authorization: Bearer REVENUECAT_API_KEY' \
--header 'Content-Type: application\/json'
--data '
{
"duration": "lifetime"
}
'