# Adapty: grant access level

The **Adapty: grant access level** Point template turns on a paid access level in Adapty for a while without a purchase, so a journey can hand out premium as a reward or a compensation.

## Configure the point

1. Drag **Adapty: grant access level** from the **Integrations** section onto the canvas.
2. Double-click the point and enter a **Step Name**.
3. In **Adapty secret key**, enter the app's secret key from Adapty: **App settings > General**. It's stored masked, like a webhook secret header — a public SDK key doesn't authorize this call, so keep it out of this field.
4. Identify whose profile to grant access to: fill either **Adapty profile ID** or **Customer user ID**, not both. **Adapty profile ID** defaults to `{{tag:adapty_profile_id}}`, the tag the Adapty → Pushwoosh integration writes when it's switched on — leave **Customer user ID** empty in that case. Fill **Customer user ID** instead, for example `{{device:user_id}}`, for an app that passes its own user ID to Adapty through `identify()`, and leave **Adapty profile ID** empty. Whichever of the two you leave empty is dropped from the request instead of being sent blank.
5. In **Access level**, enter the access level ID exactly as it's spelled on Adapty's **Access levels** page. Defaults to `premium`.
6. In **Grant for**, enter how long the access stays on, counted from the moment the traveler passes this step: a number plus a unit, for example `30m`, `12h`, or `7d`. Enter `never` for access that doesn't expire. Defaults to `7d`.
7. Click **Save**.

<Aside type="note">
This point doesn't check whether the traveler already has the access level before granting it — it sends the same request every time a traveler reaches this step, regardless of their current access. To limit how often a given traveler passes this step, use [Campaign entry limit](/product/customer-journey/journey-settings/#campaign-entry-limit) on the journey itself.
</Aside>

## Response

This point doesn't map any response data back into the journey. A failed request drops the traveler from the journey — see [Errors and failed requests](/product/customer-journey/journey-elements/integrations/#errors-and-failed-requests).