Skip to main content

​
Background

Movers now runs on standardized account workflows, and you can optionally give Movers its own workflows per app. Because a mover both gains and loses access, Movers uses two workflows: a provisioning workflow for access being added and a deprovisioning workflow for access being removed. Previously, AppStore, Onboarding, and Movers always shared a single provisioning workflow. If you configure nothing, behavior is unchanged: Movers continues to use the app’s default workflows. References Standardized Account Workflows

​
Why use this

  • Give role transitions their own logic. A mover’s access removal can run a gentler workflow (for example, suspend instead of deprovision) than a full offboarding.
  • You don’t have to configure anything. If the app’s default workflows work for role changes too, leave them as is. Movers uses the app’s default workflows until you assign it separate ones.
Before you start: you need permission to manage workflows in Lumos. If you don’t see the Account Workflows tab or can’t edit workflows, ask your Lumos administrator for access.
  1. In the left nav, go to Apps > Select the app you want to configure to open its page.
  2. Navigate to the Account Workflows tab.
  3. View existing workflows, or click Create Workflow to create a new one (details in Standardized Account Workflows)
  4. Navigate to the Provisioning and Deprovisioning workflows you want to use for Movers.
  5. In the workflow’s Used in setting, check Movers.
When checked, this workflow runs during Movers for this app. When unchecked, Movers reverts to the app’s default provisioning and deprovisioning workflow. Editing a workflow that other products use? A workflow can be shared by more than one Lumos product. If you edit one that’s also used elsewhere (for example, by AppStore or Movers), your changes apply everywhere it’s used. Lumos warns you before you save, shows you exactly which products would be affected, and offers to save your changes as a separate copy so the original stays as it is. These workflows cover the user’s account in the app. When movers grants or revokes individual entitlements (like groups or roles), Lumos uses the default provisioning and deprovisioning workflow configured for that entitlement on the app’s Permissions tab.

​
Notifications

  • The person changing roles is not emailed about each access change. Normally, Lumos messages a user as their access requests move along (created, approved, completed, removed). Mover-driven changes skip these messages, so the person isn’t notified about every app being added or removed during their transition.
  • Task Summaries now cover Movers workflows. To enable digests for Movers tasks, go to Settings > Notifications > Task Summaries and select the Movers option.