Feature Request: Source-Filtered Embedded Assistant

Feature Request: Source-Filtered Embedded Assistant

What
Enable customers to create an embedded assistant experience that is restricted to a defined set of approved knowledge sources. When a colleague interacts with the embedded assistant, responses should only be generated from those configured sources rather than the broader set of content available to the user through Artey.

For example, CVS Health could create a Policy & Procedures Assistant, connect only approved policy and procedure sources, and embed that assistant within a relevant experience. The assistant should answer questions using only those sources and clearly indicate when an answer cannot be found within them.

Why
This would allow us to create focused, trusted AI experiences for specific use cases while maintaining the broader Artey experience for enterprise capabilities. It gives colleagues confidence that answers within a specialized assistant are grounded specifically in the authoritative content intended for that experience.

Acceptance Criteria

• Admins can configure an embedded assistant with a defined set of knowledge sources.

• Users interacting with that assistant can receive answers only from those configured sources.

• Content available elsewhere in Artey is excluded from retrieval for that experience.

• Existing user permissions and source-level access controls continue to apply.

• If the configured sources do not contain an answer, the assistant does not fall back to other Artey sources.

• Responses retain appropriate source citations.

• The experience can be embedded within a customer-owned web application or digital experience.

• Configuration can be reused across multiple users without individually configuring the experience for each colleague.

Potential Technical Approach
The Conversations API may provide the underlying conversational interface because Moveworks documents it as supporting custom user-facing chat surfaces embedded in customer-owned applications.