> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.moveworks.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server. # Configure EmployeeWorks on Web (Formerly Slate) Surface the Moveworks AI Assistant inside the ServiceNow Employee Center with EmployeeWorks on Web (formerly Employee Slate), the co-branded experience that brings knowledge search, form submission, and ticket actions to your Employee Center. **Deploying to multiple ServiceNow environments? Plan for it up front.** The connector, identity, knowledge, forms, and ticketing configuration must be completed **once per ServiceNow environment**. One Moveworks tenant connected to three ServiceNow environments (dev, test, prod) means three sets of Moveworks-side configuration. Moveworks tenant access and SSO are one-time setups. This is one of the most common causes of failed EmployeeWorks on Web implementations. **For administrators.** EmployeeWorks on Web is not a standalone product: it is a surface on top of a configured Moveworks platform. Everything it exposes to end users comes from the configurations in the previous four guides. This page covers the prerequisites, the per-environment planning rule, and a validation checklist; the [Employee Slate (Powered by Moveworks) Implementation Guide](https://www.servicenow.com/community/employee-center-articles/employee-slate-powered-by-moveworks-implementation-guide/ta-p/3541697) on the ServiceNow Community then walks through the experience configuration itself. ## Before You Begin Two tiers of prerequisites: * **Required before EmployeeWorks on Web can be set up at all:** [Connect ServiceNow](/ai-assistant/getting-started/implement-on-servicenow/connect-servicenow) complete end to end (update sets, connector, user ingestion, Bot Account, Bot Access Rule). Without the connection and the user roster, the experience cannot identify the logged-in employee or reach ServiceNow. * **Required for a functional end-user experience:** [Configure Enterprise Search](/ai-assistant/getting-started/implement-on-servicenow/configure-enterprise-search), [Configure Forms](/ai-assistant/getting-started/implement-on-servicenow/configure-forms), and [Configure Ticketing](/ai-assistant/getting-started/implement-on-servicenow/configure-ticketing). The experience will configure without these, but end users would get no knowledge answers, no form submission, and no ticket actions. Complete all three before letting real users in. You also need: * **Employee Center** entitlement on your ServiceNow instance * **ServiceNow Zurich Patch 9 (ZP9)** or later, and a Moveworks license ## Procedure ### 1. Validate the Moveworks Platform Before opening the implementation guide, run this checklist against your Moveworks tenant: * [ ] You can log in to **My Moveworks** for your tenant. * [ ] **Moveworks Setup** loads and the navigation modules are visible. * [ ] In **API Playground**, your ServiceNow connector returns a `200` on a `GET /api/now/table/sys_user` call. * [ ] In **Imported Users**, your own user appears and **Enabled Users** is greater than zero. * [ ] Asking the AI Assistant a knowledge-base question returns a relevant answer with a source citation (wait for initial search ingestion to complete). * [ ] Asking the AI Assistant for something a catalog item covers surfaces the matching form. * [ ] Filing, querying, commenting on, resolving, and reopening a ticket through the AI Assistant all succeed. **If any box is unchecked, return to the corresponding guide and complete it first.** Configuring the experience on top of an incomplete platform is the most common reason setup fails, and the failure modes are confusing: incomplete answers, missing user data, and ticket errors that look like experience bugs but are platform gaps. ### 2. Configure the Experience Follow the [Employee Slate (Powered by Moveworks) Implementation Guide](https://www.servicenow.com/community/employee-center-articles/employee-slate-powered-by-moveworks-implementation-guide/ta-p/3541697) on the ServiceNow Community for the end-to-end experience configuration inside Employee Center. ## Result The Moveworks AI Assistant is live inside your ServiceNow Employee Center: employees can ask questions, submit catalog forms, and act on their tickets without leaving the portal. ## Troubleshooting EmployeeWorks on Web is a surface; when it "doesn't work," the question is almost always *which platform layer is missing*, not *is the experience broken*: * **No answers returned:** re-run the validation checklist. Search's initial ingestion takes approximately 12 hours; if you configured search recently, the index may not be populated yet. * **Can't file or query tickets:** exercise the ticket actions directly in the AI Assistant. If they fail there, fix the [ticketing configuration](/ai-assistant/getting-started/implement-on-servicenow/configure-ticketing); the experience inherits the failure. * **Doesn't recognize the logged-in employee:** confirm the employee appears in **Imported Users** and counts as Enabled. Start with the user ingestion section of [Connect ServiceNow](/ai-assistant/getting-started/implement-on-servicenow/connect-servicenow). * **The implementation guide references a product setting you don't see:** some settings are managed by Moveworks. Contact your Moveworks account team. ## What to Do Next * Complete the [Launch Checklist](/ai-assistant/getting-started/moveworks-best-practices/how-to-enable-your-moveworks-assistant/go-live-checklist) before announcing the experience to employees.