Making your Policies Active / Inactive

By default, newly created Access Policies are Inactive

​

Background

Policies in Lumos let admins automate employee onboardings — for example, defining which apps a new hire on a given team should automatically receive on day one. There are times when you want to draft a policy without it running yet, pause a policy temporarily, or stop a policy from triggering on future onboardings altogether. Each policy has a status — Active or Inactive — that controls whether it applies to future onboardings. Active policies run on any new onboarding that matches their criteria while enabled. Inactive policies sit paused: they remain in Lumos and you can keep editing them, but they won’t trigger on any onboarding until you reactivate them. This provides time to edit and finalize a policy before it actually takes effect.

​

Steps

​

1. Go to Access Policies Table

In your Lumos nav, head to Access Policies under Inventory.

Tip: Use the tabs at the top of the table (All Policies, Active Policies, etc.) or the filter bar to narrow down to the policies you want to act on. You can save a custom view if you regularly need to review a specific subset.

​

2. Toggle a single policy to make it active/inactive

Click the Active toggle in the rightmost column of any row to flip the policy on or off. The change takes effect immediately.

• Active (toggle on) — The policy applies to future onboardings that match its criteria.
• Inactive (toggle off) — The policy does not apply to any future onboardings.

​

3. Activate/deactivate policies in bulk

If you want to update several policies in a single action:

1. Click the checkbox on each row you want to update, or use the header checkbox to select all visible rows.
   
2. Once rows are selected, the bulk action bar appears at the top of the table.
3. Click Activate or Deactivate to update all selected policies.
   
4. A confirmation modal appears with a summary of what will happen:
   • Activate: “New hires will automatically get the access defined in these policies during onboarding.”
     
   • Deactivate: “New hires will no longer get the access defined automatically. This won’t affect users who were already onboarded.”
     
5. Click Activate or Deactivate to confirm. The selected policies update immediately.

​

Defaults and behavior

• Existing policies default to Active. Any policy that already existed before this feature shipped remains Active so current onboarding behavior is preserved — no action needed.
• Newly created policies default to Inactive. New policies start paused so you can review and finalize them before they begin applying. Set the policy to Active when you’re ready.
• Activating or deactivating a policy is not retroactive. Status changes only affect onboardings that happen after the change. Activating a policy will not grant access to users who were onboarded before, and deactivating a policy will not remove access from users who were already onboarded under it.

​

Common scenarios

​

I’m drafting a new policy and want to review it before it goes live

New policies default to Inactive, so you can build, configure, and edit freely without affecting any onboardings. When you’re ready for the policy to start running, toggle it to Active.

​

I want to temporarily pause a policy without deleting it

Toggle the policy to Inactive. Lumos keeps the policy and its configuration intact — it just won’t trigger on any onboardings until you flip it back to Active.

​

A policy I didn’t intend to enable is granting access to new hires

Toggle the policy to Inactive to stop it from applying to any further onboardings. Note that deactivating doesn’t remove access from users who were already onboarded under the policy — to stop in-flight onboarding workflows, see How to bulk cancel Offboarding and Mover workflows.

​

FAQs

​

Will activating a policy apply it to users who were onboarded before?

No. Activating a policy only affects onboardings that occur after the change. Users who were already onboarded won’t retroactively receive the access defined in the policy.

​

What happens to users who were already onboarded if I deactivate a policy?

Deactivating a policy doesn’t affect users who were already onboarded — their existing access stays in place. Only new hires onboarded after the change are affected (they won’t receive the access defined in the policy).

​

Why does my new policy default to Inactive?

So you have time to review and finalize it before it starts affecting employees. Once you’ve confirmed the policy is correct, toggle it to Active.

​

Why are all my existing policies set to Active?

Existing policies were already running before this feature was introduced. They default to Active to preserve current behavior — no action is needed unless you want to pause one.