> This page is for Assistant Platform. > 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. # Productivity Assistants > **Controlled Availability** > > Productivity Assistants are in Controlled Availability. Capabilities, limits, and interface labels described here may change before general availability. To request access, contact your Moveworks account team. A Productivity Assistant is a focused assistant for when you need **scoped knowledge for a specific audience, persona, or methodology of doing work**. Where the Enterprise Assistant is designed to be inclusive and all-encompassing — serving every requester across every system — a Productivity Assistant is tuned for one team's content, tools, voice, and output format. The result is answers that are more useful, more usable, and shaped in the voice that specific team actually uses — not diluted by content meant for other audiences. Productivity Assistants **unlocks productivity for the entire workforce** — new personas, new use cases, new domains, without coding experts needing to deliver each one. ## Why Productivity Assistants? * **Discovery and recall.** Users find it hard to understand what a single assistant that "does everything" can actually do. A Productivity Assistant has a descriptive name and a clear scope, so people know when to reach for it — and recommend it to teammates. * **Depth of reasoning on scoped work.** Productivity Assistants run on the latest reasoning models and the **Agentic Orchestrator**, a next-generation reasoning harness. They can run long-running tasks, dig across every system the user already has access to, surface sources the user didn't know existed, and transform results into a decision-ready artifact. * **Fit for a specific audience, methodology, or voice.** Enterprise-wide reasoning has to serve every requester and every fulfiller. A Productivity Assistant lets a team scope content and tune output to its own vocabulary and conventions — legal with its specific voice, service-ops with fulfiller-facing content only, analytics with structured outputs — so results are useful and usable the first time. ## Example Productivity Assistants ### AI Sales Coach A sales rep's in-the-flow coach. Prep for customer meetings, sharpen discovery, handle objections, and position against the competition. ### Time Entry Assistant Automates daily time entry from your calendar. Reads your meetings, categorizes them against your projects, and submits entries into your time-tracking system — all from chat. ### Product Operations A product-operations assistant for the full project lifecycle. One place to work through strategy and requirement writing, product and support escalations, roadmaps, launches, and digests. ## Building Blocks | Capability | Description | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Instructions** | Text appended to the system prompt on every turn. Shapes tone, workflow, and output format. *Limit: 30,000 characters.* | | **Knowledge** | Scope what the assistant retrieves from Enterprise Search. | | — Content | Individual files or KB articles. | | — Workspace | SharePoint Sites, ServiceNow Knowledge Bases, Confluence Spaces, OneDrive folders. | | — Channels | Slack channels. | | **Skills** | Uploaded instruction bundles (`.zip` or `.skill` with a `SKILL.md`) that the assistant loads when a request matches the Skill's description. Skills are instructions, not tools. *Limit: 100 Skills.* | | **Native Tools** | Built-in Moveworks tools the assistant can call: World Knowledge, People Directory, and more (such as forms). | | **Apps** | Third-party systems the assistant can call. Users still need their own permissions in each system. | | — Enterprise Search systems | ServiceNow, SharePoint, Content Gateway, and other sources your admins have approved. | | — MCP servers | Any MCP server connected in MCP Workspace. Users authorize each server themselves. *Limit: 50 MCP servers.* | | **Tool Studio Tools** | Custom plugins built in Tool Studio. Availability varies by plugin. | | **Sharing** | Who can open the assistant: everyone, specific people by email, or only you. | ## Notifications Ambient agent notifications fired from Tool Studio can be routed to a specific Productivity Assistant instead of the Enterprise Assistant. When the user replies, the follow-up runs inside that assistant's session — with access to its tools, knowledge, and voice. If no destination is set, notifications fall back to the Enterprise Assistant. Supported surfaces: EmployeeWorks (notification panel; click opens a scoped thread), Microsoft Teams and Slack (ChatBot DM). Button/Action support on Productivity Assistant notifications is not yet available. **To route a notification to a Productivity Assistant:** 1. In Tool Studio, open the ambient agent plugin you want to route and click into the **System Body** action. 2. Scroll to **Notification destination** and pick the Productivity Assistant by **ID and name**. If you're editing the config directly, set `agent_config_id` under the `Notify` block to the assistant's ID. 3. Fire a test payload against the webhook trigger. Confirm the notification appears in the destination assistant for users who have access to it. ## Where End Users Find Them Each assistant keeps its own conversation history for each user, separate from the main Moveworks AI Assistant. * **EmployeeWorks web app.** * Admins can pin these assistants directly for end users in their left side navigation. * Users can also go into **Browse assistants** to see all assistants shared, and pin their favorite assistants. * **Slack, Teams, and Conversation API **-- talk to your Moveworks representative extending Productivity Assistant's reach into other surfaces employees use like chat platforms, and via conversation API. ## Configuration In Setup, go to **AI Assistant > Advanced Settings > Productivity Assistants** and turn on **Enable Productivity Assistants**. This enables Productivity Assistants for end users to interact with. Super Admins and Productivity Assistant Admin can administrate Assistants -- meaning they can view and edit and delete any assistant configurations, regardless of whether they created it. **(WIP)** In Setup, to enable users to create Assistants, these are derived from **Productivity Assistants** application roles. * Roles can be default set across all employees. * To give individual users more privilege, you can go to Roles & Permissions to assign individual users a more privileged role than the default role. | Role | What it allows | | ------------------------------------ | ------------------------------------------------------------------------ | | Productivity Assistant Admin | Manage roles and all Productivity Assistants in the organization. | | Builder (Personal Use) | Create assistants for your own use. | | Builder (Share with People) | Also share assistants with specific people. | | Builder (Share with People & Groups) | Also share assistants with groups, when group sharing becomes available. | | Builder (Company-wide Sharing) | Also share assistants with everyone. | ## Next Steps #### [Create a Productivity Assistant](/ai-assistant/productivity-assistants/create-a-productivity-assistant) Configure instructions, tools, knowledge scope, Skills, MCP servers, and sharing step by step. #### [Examples](/ai-assistant/productivity-assistants/use-cases) Starting configurations for common assistants. #### [Agentic Orchestrator overview](/harness/agentic-orchestrator) How the runtime composes instructions, Skills, tools, and plans on every turn.