Configuring Custom Intake Fields

Last updated: October 7, 2024

Background

Sometimes your provisioners need additional information to properly provision the user to an app or permission. 

Say goodbye to the days where you add this in the instructions section of the form in the hopes that requesters read it (don't worry, they likely won't 😉) and then have to go back and forth with them in Slack to get the necessary info. 

You can now configure intake fields that need to be filled out before creating a request in the AppStore. Now you can automatically get your requester's github username in your provisioning notification, no back and forth needed!

Instructions

1. Navigate to the app's AppStore settings!

You should see a new section called Custom Fields:

2. Click +Add New Field, and you'll select either a Text or Single Select option. 

If Text Field:

Add your prompt (I.e. 'Please enter your Github username') & add an optional description.

If Single Select Dropdown:

Add your prompt & add an optional description. Click "Next", which will pop open a modal for you to enter in your dropdown values. You can use enter as your delimeter here and we'll support up to 50 values in the dropdown. 

3. You're all set!

When users request this app, they'll now be asked to populate these required values! 

FAQs

1. Where can I see the user responses to the custom intake form questions?

Notifications (Slack, email), the Lumos Task Center, ITSM, SIEM, and the Activity Log.

2. Can I configure a multi-select dropdown?

This is not available today.

3. How does this work with New Hire Onboarding rules?

We’re working on a smoother experience to handle this, but in the interim, the admin will need to set the required values at the creation of the onboarding rule.

4. What is the max number of custom intake fields I can configure on an app?

Four, but please reach out to your CSM if this doesn’t work for your use case!

5. What happens if I delete a custom intake field while there are in-flight requests?

Nothing! We’ll keep the data on the request, but the request will still proceed.

6. As an approver, can I make updates to these answers while the request is live?

Soon! 👀 This Is coming shortly, stay tuned!

7. Can I configure fields to not be required (optional)?

This is not available today, but you can continue using the instructions field to instruct users to add optional fields in the business justification!