Plans and AI access
Understand Grunt ONE, Grunt AI, viewer and editor access, and the client requirements for your workflow
You can use Grunt ONE with your organization's existing AI assistant. You need a Grunt ONE plan and access to a compatible assistant; a separate Grunt AI subscription is optional for this workflow.
#Grunt ONE and Grunt AI
| Workflow | Access you need |
|---|---|
| Create and refine Grunt charts through an external assistant, such as Claude | Grunt ONE and an assistant configuration that supports the required Grunt connection. Your assistant subscription is separate. |
| Refine an asset visually in your browser | Grunt editor access and permission to edit the asset. |
| Use the Grunt AI chat inside the Grunt PowerPoint add-in | Access to Grunt AI through your organization's plan. See Grunt AI in PowerPoint. |
| Have Claude work on an open PowerPoint presentation | The planned Grunt ONE live PowerPoint workflow and its supported Claude configuration. This capability is in development. |
You can combine Grunt ONE and Grunt AI if your team wants both external-assistant workflows and Grunt's own PowerPoint chat. Confirm the products, editor access, and third-party subscriptions included in your package with Customer Success.
#Viewing and editing
Recipients can view a shared report or Grunt visual without an editor license, provided they have permission to access the content. Offline reports include the visuals saved in the file; retrieving newer content requires access to the relevant Grunt services.
Editing Grunt charts and tables in PowerPoint or the Web Editor requires the applicable Grunt editor license or organization entitlement, as well as permission to edit the asset. An edit link supplies permission to the asset; it does not purchase or assign a product license. For an embedded Web Editor integration, your organization supplies the editor entitlement through its configured integration.
Editing a chart does not automatically update a report's written analysis or synchronize other copies. See Connected workflows for refresh and import behavior.
#Choose the client for your workflow
An AI subscription alone does not establish that the required connector, skill, or PowerPoint integration is enabled. Confirm the exact client and workflow with your organization's AI administrator and Grunt before starting an evaluation.
| Workflow | What to confirm |
|---|---|
| Chart and table tools through MCP | Your client supports remote MCP over Streamable HTTP and the chosen authentication flow. Follow Connect and authenticate. |
| HTML reports and presentation files | Your assistant can use the required Grunt skill and create the deliverable files. Agree which client, such as Claude Cowork or Claude Code, is supported for that workflow. |
| Live control of an open PowerPoint deck | Confirm the Claude for PowerPoint configuration, compatible Grunt add-in, and availability of the live connection. Generating a presentation file is a separate workflow. |
If Copilot is your organization's only approved assistant, confirm the availability of the required Grunt integration before planning an evaluation. Support for one assistant or workflow does not establish support for another.
#Agree your package and rollout
Contact Customer Success to confirm pricing, bundling, and whether a departmental rollout is available under your agreement. Include the proposed users, editors, AI client, and hosting model. Departmental pricing and organization-size calculations require an agreed quote.
A commercial agreement and technical access are separate milestones. Use the rollout status to identify capabilities to discuss, then agree the features and access enabled for your organization. Roadmap dates do not by themselves activate a feature.