AppStore Rollout Setup Checklist
Last updated: October 8, 2024
After this article...
You'll know exactly what steps need to be completed in Lumos to get your AppStore ready for rollout!
🔌 Configure Integrations
You don't need to connect every single app to Lumos to use the AppStore. To understand why, check out this article.
Lumos will leverage your identity provider (IdP) to provision where possible and will route requests for other apps to the right admins for manual provisioning.
This section might look daunting, but don't worry. Most companies can finish the steps here in less than an hour.
Step | Do I need to do it? | Why do it? |
Connect your email provider | Required | Lumos will discover apps your employees are using so you can quickly add them to your AppStore. |
Connect your identity provider (Okta, etc.) | Required | Lumos can discover apps managed through your IdP so you can add them to your AppStore. Note: If your email provider and identity provider are the same, you can skip this once you've connected your email provider. |
Optional | Log tickets in your ITSM for compliance so you can start using the AppStore for all access requests! | |
Connect Slack | Highly Recommended | Help access requests get done ASAP by routing tasks through Slack. |
Highly Recommended | Makes sure that notifications are delivered through Slack in addition to (or instead of) email. | |
Put Lumos behind your IdP | Recommended | Roll out the AppStore when you’re ready by putting Lumos behind your IdP. Note: If you’re using Google/Microsoft as your IdP, this is already done when you connect them to Lumos! If you’re using another provider, please contact Lumos Support to set this up. |
Required (if using manager approvals) | Make sure that Lumos is sourcing employee manager info from the best place. | |
Required | Helps Lumos pull employee status from the correct sources so that everyone can access the AppStore! | |
Configure your Login Provider | Required | Set how employees will log into Lumos so they can access the AppStore. |
➕ AppStore Settings
You’re probably tempted to add a lot of apps to your AppStore — it’s addicting to automate so much manual work so quickly.
Step | Do I need to do it? | Why do it? |
Add your highest-value apps to your AppStore | Required | Make sure that you can start automating the highest-value apps! |
Make sure your apps have approvers, if needed | Optional | Approvers are only needed if the app is not manually provisioned and you need someone to approve the request before provisioning. |
Make sure that every app has an App Admin | Required | App Admins are notified if there are issues provisioning access to an app — they play an important role! |
Highly Recommended | This lets your employees request apps that aren’t in your AppStore yet. |
🧪 AppStore Testing
You don't need to test every app! Just make sure you test out a few sample workflows so that you can get a feel for how things are working.
Step | Do I need to do it? | Why do it? |
Test the workflow for a manager-approved app | Highly Recommended (if using manager approvals) | Make sure that manager approvals are working as expected. Let your manager know that you’re testing beforehand! 🙂 |
Test an app without manual steps (if you have one) | Highly Recommended | See how the AppStore works for apps where no manual provisioning is needed. Is access (a tile) for the app being created in your IdP as you expected? |
Test a manually-provisioned app | Highly Recommended | Test this on an app where you’re an App Admin. Is the list of admins being properly notified? |
Test the /request workflow in Slack | Highly Recommended | Make sure that Slack requests are working as expected! |
Test the Custom Request workflow | Highly Recommended | Early on, more of your requests will be custom until you start adding more apps. Is this flow creating a ticket in the right place so that you can easily follow up with requesters? |