Genie One scheduled tasks can now email colleagues—treat the recipient list as a data-delivery surface
Databricks expanded recurring Genie outputs beyond the task owner. The useful rollout question is no longer only whether the prompt is correct, but who receives the rendered result and attachment.
Databricks has expanded Genie One scheduled tasks so they can email other users in the same organization, rather than sending results only to the task author. The November 12 release note makes the recipient change explicit; the product documentation says each run posts into a chat thread and sends an email containing the results, any visualizations, and a PDF attachment of the output. Databricks release notes Scheduled-task documentation
That turns a personal automation feature into a lightweight recurring distribution channel. A user can create a task in natural language or through a manual form, where Databricks exposes fields for the title, instructions, connections, schedule and timezone. Authors can also run the task immediately, inspect past runs, edit it, delete it or mention it from a new request. Scheduled-task documentation
The new control point is the rendered output
The operational unit to review is not just the prompt. It is the email package: answer text, visualizations and an attached PDF. Those artifacts can be forwarded, retained or downloaded outside the original chat thread. Databricks documents the package and the new ability to address other organizational users, but the cited scheduled-task section does not describe a recipient-specific source-permission recheck. Teams should therefore test the behavior with representative recipient accounts before using the feature for sensitive recurring reports. Scheduled-task documentation
A sensible rollout starts with three checks:
- Use a low-sensitivity report first. Validate the exact email body, visualization content and PDF before adding a broader recipient list.
- Review the configured connections. The manual task form includes a Connections field, so the delivery review should cover every source the scheduled instruction can reach.
- Re-test after edits. Use Run now after changing instructions, connections or recipients, and retain the resulting thread as the review record.
These are rollout recommendations, not controls Databricks says it enforces automatically.
Why this small release matters
Scheduled analytics often become de facto reporting infrastructure. Genie One now supplies the creation interface, execution history, recurring cadence and outbound email package in one workflow. That is convenient, but it also means a seemingly minor recipient edit can change the audience for a generated analysis and its PDF copy. Scheduled-task documentation
Administrators do not need to block the feature to manage that risk. They do need to inventory shared schedules, assign an owner, review recipient lists and treat output previews as part of the approval process. The release is most useful when teams pair its convenience with the same distribution discipline they already apply to emailed dashboards and scheduled BI exports.
sources
- AI/BI and Genie One release notes 2026docs.databricks.com
- Chat in Genie One — scheduled tasksdocs.databricks.com
comments · 0
- Databricks made ai_decide more accurate—but the model behind the SQL function can change againNov 17, 2026
- A new French open-data test finds architecture matters less once the local model reaches 3B parametersNov 17, 2026
- ThoughtSpot’s Data Cache is fast—but cached and live answers are not always equivalentNov 17, 2026