The Onboarding Stage setting in Moveworks Setup controls which platform capabilities are active for your organization. As your deployment progresses from initial configuration through to full production, the onboarding stage determines whether analytics populate, whether employee data is fully synchronized, and whether Moveworks proactively monitors your environment.
To find this setting, go to Moveworks Setup and open Org Settings.
presales
Used for pre-contract evaluation environments. Data processing and indexing are not active. This stage is managed by your Moveworks team.
dev_integration
An early-stage environment for initial integration work. Data begins flowing into the platform and analytics pipelines start receiving org data, but employee directory sync and active monitoring are not yet enabled.
prod_integration
Integration testing against production-grade infrastructure. Configuration validation alerts are active, but analytics pipelines and full employee sync are not yet enabled.
it_testing
Your IT team is validating the deployment before a broader rollout. Analytics data begins populating, and configuration validation alerts are active. Employee directory sync is not yet fully enabled.
limited_rollout
The assistant is live for a subset of employees. Full employee directory sync is active. Analytics and reporting populate normally. This stage is used for phased or pilot rollouts before moving to full production.
live
Full production. All platform capabilities are enabled: analytics populate, employee data is fully synchronized, and Moveworks proactively monitors your environment against operational SLAs.
offline
The org is temporarily inactive. Data processing and active monitoring are suspended. Use this stage when the deployment is paused.
offboarding
The org is in the process of being decommissioned. Processing and monitoring are suspended.
sandbox
A fully isolated environment used for demos and internal testing. Sandbox orgs are excluded from all production data pipelines, analytics, and monitoring. Errors in sandbox environments are suppressed rather than surfaced. This environment does not reflect production behavior.
The table below summarizes which platform capabilities are active at each stage.
Data indexed and processed: The assistant can search and retrieve knowledge from your connected sources.
Analytics and reporting: Usage data populates in your analytics dashboards. Note that analytics also require the Go-Live Date to be set in Org Settings. Data before that date is not included.
Employee directory sync: Employee records are fully synchronized and treated as production data.
Proactive SLA monitoring: Moveworks actively monitors your environment against operational SLAs and is alerted if thresholds are breached.
Configuration validation alerts: Moveworks is notified if configuration issues are detected in your connected integrations.
The Deploy Channel field specifies the Slack channel where your Moveworks deployment team receives operational notifications. These include indexing status updates, validation errors, and login flow issues.
The deploy channel must be set and must match the format deploy-<org-name>, support-<org-name>, or ops-deploys-<org-name>. If it is not configured, notifications will not be delivered to your team’s channel.
The deploy channel is also required for your org to appear in certain analytics pipeline reports, in addition to being in an analytics-eligible stage.
If your org is set to live but the Deploy Channel is not configured, your team will not receive operational notifications and your org may not appear in all analytics reports.
Before setting your org to live, confirm the following:
Stage changes take effect on the next processing cycle for your org. Contact your Moveworks team if you are unsure which stage your org should be in.