> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Setting Default AppStore Entitlements

> Set a default entitlement for an AppStore app in the Default Permission dropdown and learn how No default and hidden default entitlements behave under each Provisioning Method.

## Background

Some of your apps today may have entitlements representing licenses or access rights that can be requested for your app.

Depending on your app's Provisioning Method, you may want to set a default entitlement so that there's a higher chance of ensuring users are getting the correct access to their applications.

\[This is particularly helpful for apps whose entitlements are Assign to App Permission, Defaulted, which has traditionally defaulted to the first entitlement (I.e. highest priority group in Okta) listed in Lumos.]

## Instructions

### 1. Go to the app's AppStore configurations and you'll see a new dropdown called Default Permission.

You can click the dropdown, which will allow you to configure the default entitlement for that app.

## FAQs

#### 1. What does No default mean?

No default means that you have not configured an explicit entitlement override for this application. Depending on the Provisioning Mode, the behavior will be slightly different.

If it's Assign to App Permission, Requester-Selected, it will require the end user to select the entitlement.

If it's Assign to App Permission, Defaulted, it will still default to the first option.

#### 2. What happens if I have set a default entitlement that isn't visible in the AppStore?

For example, you have the default entitlement set to Entitlement X, and Entitlement X is hidden from the AppStore. When you go to request the app, Lumos treats it like no default was set (see FAQ 1).