> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumos.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Onboarding Workflows
### After this article
You'll know how to set up automated onboarding workflows that run whenever a new employee is detected in your organization and grant initial access to critical systems.
## Background
When a new employee joins your organization, there's a specific sequence in which their accounts should be created. Identity Provider (IdP) and Email Provider accounts need to be set up first, as they're the foundation for accessing other tools.
Onboarding Workflows in Lumos allow you to create a structured, automated process that ensures accounts are created in the right order, with proper timing between steps.
## Configuring onboarding triggers
The first step in any onboarding is determining when the onboarding should start. Lumos supports 2 methods of automating new hire onboarding:
As a best practice, automate onboarding workflows based on a start date. This allows you to sync start dates multiple days in advance of the onboarding so that access is ready on the employee's first day.
1. **Immediately Upon Account Creation**. When you select this method, onboarding workflows will run automatically for all new hires as soon as a new identity is detected from one of your [Source of Truth](/kb/appstore/source-of-truth/source-of-truth) systems.
2. **Based on Start Date.** When you select this method, onboarding workflows will run automatically a certain number of days before the "start date" for the employee, detected through your source of truth system
## 7-Day Lookback Window
When you enable an automatic Onboarding workflow, Lumos uses a 7-day lookback window to determine which users are eligible. This means the system evaluates users whose triggering event occurred within the past 7 days.
**Onboarding triggers and how the lookback applies:**
* **X days After Account Creation** — Lumos looks at the user creation date in Lumos. Any user created within the past 7 days of the specified date who is active and has no prior onboarding record will be matched.
* **X days Before Start Date** — Lumos looks at the user Start Date. Any user whose Start Date falls within the past 7 days of the specified date will be matched.
**Example:** If you enable a "0 Days After Account Creation" onboarding trigger on April 7th, any user created between April 1st–7th will be eligible. Users created more than 7 days ago will not be affected.
To modify this Lookback Window duration, contact [support@lumos.com](mailto:support@lumos.com).
## Configuring onboarding workflows
After configuring when an onboarding is triggered, you can also choose to run specific actions during an onboarding workflow. Lumos supports 4 actions in onboarding workflows today, described below.
#### Create Access Request Step
This step kicks off an access request for application or permission. Use this step for Identity Provider or Email Provider accounts, which need to be created before all other access.
**Key Settings:**
* **App:** Select the specific app to request
* **Permission:** If the app supports more granular access, choose which permission to provision for the employee
* **Access Length:** If the app supports time-based access, choose which access length you want to request
* **Business Justification:** Enter a default business justification, which will be used to track why access was granted
#### Wait Step
This step adds a delay before proceeding to the next step. This is useful when you need to ensure that an account is fully provisioned before granting additional access.
**Key Settings:**
* **Wait Duration:** Specify how long to wait before continuing to the next step
* **Duration Unit:** Select minutes, hours, or days
#### Execute Access Policies
This step evaluates rules that you've configured (e.g., if title="Product Manager", then you get access to Loom), and automatically kicks off requests for other software access based on the rules.
### Generate Email
This step allows you to configure a set of rules for how to generate an email address. By default, Lumos ensures that all created email addresses are unique, and if the generated email address is not unique, you can use fallback rules to design the right behavior.
**Key Settings**
* **Generation Rules:** Rules configured using the [Lumos Expression Language](/kb/_uncategorized/using-the-lumos-expression-language-in-workflows) to generate an email address based on identity attributes. If the first rule results in an invalid or non-unique email, Lumos will "fallback" to subsequently defined rules
## Viewing Workflow Progress
Onboarding Records allow you to monitor the progress of your onboarding workflows to ensure they're running as expected. In order to view an Onboarding Record, navigate to Employee Lifecycle > Onboarding, and select the onboarding that you would like to view.
## FAQs
### Are onboarding workflows triggered immediately?
Lumos will trigger an onboarding within 1 minute of the scheduled start time. However, it may take up to 5 minutes to notice workflow progress within the application.
### What if a step in the workflow fails?
If a step fails, the workflow will pause at that step and you'll receive a notification. You can then investigate the issue, resolve it, and resume the workflow from the Workflow Records page.
### How do I modify an existing workflow?
Navigate to the Onboarding page, select settings, and click the "Edit" button on your onboarding workflow. Note that changes will only affect future workflow runs, not ones that are already in progress.
### Can I see a history of completed onboarding workflows?
Yes, all completed workflows are available in the Workflow Records section, where you can filter to view only onboarding workflows and their outcomes.
## Other questions?
Contact [support@lumos.com](mailto:support@lumos.com) or your CSM.