This set builds vocabulary for AI assistants embedded in everyday productivity tools.
0 / 5 completed
1 / 5
At standup, a dev mentions an AI assistant embedded directly inside a word processor that can draft, summarize, and rewrite content based on a plain-language prompt. What is this integration called?
An in-app AI copilot assistant is embedded directly inside a productivity application, like a word processor, letting a user draft, summarize, or rewrite content from a plain-language prompt without leaving the document they're working in. This tight integration reduces the friction of switching to a separate AI tool and copying content back and forth. It reflects a broader trend of generative AI capability being embedded directly into existing productivity software.
2 / 5
During a design review, the team wants an AI assistant to answer questions using only the organization's internal documents and data, not general public knowledge. Which capability supports this?
Grounding an AI assistant's responses in an organization's own internal documents and data, rather than only its general public training knowledge, ensures answers reflect the organization's actual, current, and often confidential information. This is essential for enterprise use cases where generic public knowledge wouldn't include internal policies or proprietary data. Enterprise AI copilots are typically built specifically to support this kind of internal data grounding with appropriate access controls.
3 / 5
In a code review, a dev asks the AI assistant to generate a summary of an hour-long meeting recording, highlighting action items assigned to each attendee. What does this represent?
AI-generated meeting summarization processes a recording or transcript and extracts a condensed summary along with specific action items assigned to attendees, sparing someone from manually reviewing the full recording and writing that summary by hand. This automation is a common productivity application of generative AI embedded in collaboration and communication tools. It's especially valuable for attendees who couldn't join the live meeting.
4 / 5
An incident report shows an AI assistant surfaced a snippet of a confidential document to a user who shouldn't have had access to it. What practice would prevent this?
Ensuring an AI assistant respects the same existing document permissions and access controls that govern normal human access, rather than assuming grounding automatically inherits correct permissions, prevents the assistant from surfacing content a given user shouldn't be able to see. Verifying this explicitly, rather than assuming it works correctly by default, is essential before rolling out an enterprise AI assistant with access to sensitive internal data. This permission-respecting behavior is a critical security requirement for any enterprise-grounded AI tool.
5 / 5
During a PR review, a teammate asks why the team values an AI assistant grounded in internal organizational data over one relying only on general public knowledge. What is the reasoning?
An AI assistant relying only on general public knowledge has no way to answer a question about an organization's specific internal policy or proprietary data, while one grounded in internal documents can. This grounding is what makes an AI assistant genuinely useful for enterprise-specific tasks rather than only generic ones. The tradeoff is the additional complexity of securely integrating the assistant with internal data sources and their access controls.