The Problem

The Lumos AppStore let’s you configure flexible workflows to define how access should be granted and revoked from employees. These workflows are powerful, but don’t have all of the automated steps needed to handle all types of provisioning today.

The Solution

We are adding a new set of actions that will be available in your AppStore workflows to extend what is possible in the AppStore and make existing actions more clear:

• Remove from Group: remove users from a set of groups as part of your AppStore provisioning. This is useful when users are requesting access to advanced licenses (e.g. Zoom Pro) and you need to revoke other license groups (e.g. Zoom Basic) before granting access
• Request Manual Provisioning from [User]: You will be able to define which users need to provision access to the target account. This will allow you to:
  • Define different users to provision access to different permissions. For example, if you have a specialized team responsible for a set of licenses or resources
  • Request that the target user take an action before provisioning can complete. For example, for access that is provisioned just-in-time, you can request that the target user sign into the application (creating an account) before permissions are granted
• Automated Provisioning → Assign to App, Create Account, Grant Permission: we are breaking out our “Automated Provisioning” action into more granular steps, so you can see exactly what actions Lumos is taking in your downstream systems. Instead of “Automated Provisioning”, you will see:
  • Assign to App — Lumos will assign the user directly to the application tile in your IdP
  • Create Account — if an account does not exist, Lumos will create one using data from the target user’s identity
  • Grant Permission — Lumos will use an integration’s direct APIs to grant a user access to a granular resource or license