Users can message Genie directly or @mention it in a channel, and it replies in the thread using data the asker can reach through Unity Catalog and connected source permissions. Each answer cites its sources. Channel settings let admins choose between Genie One, the default, and a specific Genie Agent, and set responses to be shared with the channel or kept private.
Through MCP connectors, Genie can create or update documents, comment on tickets and update records using the user's own credentials. It asks for approval before each change runs. Users can also schedule recurring analyses delivered to their DM, upload files for analysis, and receive charts inside threads.
Admins manage AI usage in Unity Gateway, where MCP policies determine which servers and tools Genie can use, which users can reach them, and which actions need human approval. Traces record what Genie did and who asked for it. Workspaces that use Private Link are supported through context-based ingress policies.
Why it matters if you build agents
Agent builders can offer a Slack-facing assistant over governed enterprise data without building a separate permission layer, since each query runs under the asker's identity. Write actions through MCP connectors require approval, and the MCP policies and traces in Unity Gateway are where teams can set limits and audit activity. Teams using Private Link need an account admin to create a context-based ingress policy before the integration will work.
Get stories like this every weekday
One short email with the day's agent tooling news.