Configure Adaptive Access
Set up product-level and feature-level age assurance for your product in Compliance Studio, globally and per market.
Adaptive Access is configured on one screen in Compliance Studio. There you choose whether users prove their age at sign-up (product-level), when they reach a protected feature (feature-level), or both. Global settings apply in every market, and each market can override them.
Open the Global Rules screen
- In Compliance Studio, open Products and select your product.
- Under Configuration, select Engine & Overrides.
- Under Global Baseline Configuration, select Edit Global Rules.
The Global screen has these sections:
| Section | What it controls |
|---|---|
| Global defaults | The Digital Consent Age and Civil Age used across markets |
| Product-level access | Whether users prove their age at sign-up |
| Feature-level access | Whether users prove their age at protected features |
| Age Assurance Reporting (API only) | The ageAssuranceRequired value the API reports |
Feature-level access appears only when your product has permissions registered. Select Save changes to keep your edits, then publish them (see Publish your changes).
Product Policies
When a Product Policy is attached to the product, these settings are read-only. Change them in the policy instead.
Product-level access
Require age assurance at sign-up?
| Option | What happens |
|---|---|
| No (default) | Users sign up normally. You can still verify their age later, at features. |
| Yes | Every user who claims the trigger age or older must verify before entering. |
When you choose Yes, set Who this applies to: Every user ≥ a trigger age. Choose Civil Age (the default), Digital Consent Age, or a specific age. In each market, the trigger age is never lower than that market's Digital Consent Age. Users below the Digital Consent Age always go through Verifiable Parental Consent, whatever you set here.
Product-level access verifies every user at or above the trigger age at sign-up, including users who never reach a restricted feature. Talk to your k-ID Account Manager before you turn it on for a live product. If you don't see Product-level access on the screen, contact your k-ID Account Manager.
What it means for your code: /age-gate/check returns a CHALLENGE_AGE_GATE_AGE_ASSURANCE challenge instead of a session for users at or above the trigger age. See Product-level age assurance.
Feature-level access
Require age assurance for a specific feature? Features are the permissions registered for your product, such as targeted ads, loot boxes, or AI chat.
| Option | What happens |
|---|---|
| No | Turns off feature-level age assurance, even where the CDK says it's legally required. |
| Yes | Turns on feature-level age assurance and applies the CDK's default rules to every feature. |
| Yes, with changes | Turns on feature-level age assurance and lets you override the rules for individual features. |
Turning it on does two things. Users at or above a feature's Threshold Age must verify before that feature unlocks, and the CDK's default rules for every feature load in every market. Sign-up isn't affected.
New products start with Yes. Products created before feature-level age assurance launched show No until you change it, and a copied product keeps the setting of the product it was copied from.
What it means for your code: affected permissions carry a verifiedAgeThreshold and stay disabled until the user verifies. Your app offers the check with a /session/upgrade call. See Feature-level age assurance.
Override rules for individual features
With Yes, with changes selected, use Feature overrides to change how individual features behave:
- Select Add and choose a feature.
- Read the rule as a sentence: the feature is prohibited under one age, needs trusted adult consent until another, is off by default under a third, and triggers age assurance in the cases you choose. Each age defaults to Use CDK Default.
- Set age assurance triggered to one of:
- if the CDK says so (default): the feature asks for proof wherever the CDK's rules for the market require it.
- always: the feature always asks for proof. If neither your rule nor the CDK default gives the feature an age at which it's prohibited or needs trusted adult consent, choose one; Compliance Studio won't save always without it.
- never: the feature never asks for proof.
The age at which a feature asks for proof is its Threshold Age, which comes from the feature's ages in the rule. There's no separate threshold setting. Your app reads the resulting age from each permission's verifiedAgeThreshold.
To cover only some features, select Yes, with changes, then set every feature you don't want checked to never. Features you don't touch keep the CDK's default rules.
Age Assurance Reporting (API only)
Should the API report that age assurance is required? Choose Use CDK Default (the default), Yes, or No.
This only sets the ageAssuranceRequired value that /age-gate/get-requirements returns. It never starts a check, and it affects users only if your code reads the field and acts on it.
Change the settings for one market
- On Engine & Overrides, select Add Market Specific Rules and choose a market. For a market that already has rules, select Edit Override.
- On the market's screen, set Product-level access and Feature-level access for that market:
- Global Default or Use Global Setting keeps the global answer.
- No, Yes, or Yes, with changes overrides it for this market only.
- Select Save changes.
A market set to Yes for product-level access verifies every user there at or above the trigger age, even where the law doesn't require it. Confirm with your legal counsel before you override a market.
Publish your changes
Saved changes stay in your product's draft until you publish them:
- Select Push to Test and check the behavior in your test environment. See Testing and publishing.
- Select Push Live to apply them to live users.
For a production product, turning on global feature-level access is a critical change, so the button reads Submit for Review, and k-ID reviews the change before it goes live. Turning it off doesn't need a review.
Test both paths
Before you publish to live, check each path in your test environment:
- Product-level: call
/age-gate/checkwith an age at or above the trigger age and confirm you get aCHALLENGE_AGE_GATE_AGE_ASSURANCEchallenge. - Feature-level: create a session for a user old enough for a protected feature, confirm the permission has a
verifiedAgeThresholdandenabled: false, then call/session/upgradefor it.
The quick starts walk through both paths: Age assurance at entry and Age assurance at features.