Skip to main content

​
Background

Some of your apps today may have permissions representing licenses or entitlements that can be requested for your app. Depending on your app’s Provisioning Method, you may want to set a permission default 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 permissions are Assign to App Permission, Defaulted, which has traditionally defaulted to the first permission (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 Permission for that app.

​
FAQs

​
1. What does No default mean?

No default means that you have not configured an explicit permission 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 permission. 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 permission that isn’t visible in the AppStore?

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