Project management software without AI: defaults and controls

Choosing project management software without AI means checking built-in features, vendor data use and outside AI assistants separately. Turning off the visible AI features does not settle all three.

Most large project tools now include AI on their paid plans and let an admin switch it off afterwards. Trello turns it on automatically for Standard and Premium workspaces, Jira and Confluence give Rovo to everyone on paid plans, and ClickUp and Asana include it in the plan. Breeze is one of the few where the built-in AI stays off until an admin turns it on. That switch does not cover its MCP connector or live voice note transcription.

If a client forbids AI processing, check what an admin can enforce before choosing a tool. Breeze has no admin setting to block the MCP connector, and Live transcript starts on as a personal setting. Its in-app AI being off does not make it an AI-free product.

In an old stone mill, a man hangs up the key to a padlocked lever switch labelled AI while a visitor holding a contract looks on

Disclosure: Breeze publishes this page and is one of the tools compared. Where Breeze gives an admin less control than another tool, the page says so.

Contents

What does "no AI" cover?

A no-AI policy has to cover built-in AI features, the vendor's use of project data and outside assistants. A promise to a client has to close all three routes. Turning off the AI button closes only the first.

  • Built-in AI features: the summaries, writing help, agents and chat inside the tool. These send your task text to an AI model, usually run by a partner such as OpenAI, Anthropic, Google or Mistral.
  • The vendor's own use of your data: whether the vendor uses your content to improve its AI for all customers. This is a data setting, not a feature, and it can be on while every AI feature is off.
  • Outside assistants: connectors, usually built on the Model Context Protocol (MCP), that let a person's own Claude, ChatGPT or Copilot read and change data in the tool. These run under the person's login, not the admin's AI switch.

Teams asking for a tool without AI usually mean the first route, because that is what they see. One thread on r/Notion asking for alternatives without AI drew close to 200 replies. Contracts care more about the second and third, because that is where client data leaves the tool.

Which tools enable AI automatically?

Of the six tools checked besides Breeze, two say so in writing: Trello, and Jira and Confluence through Rovo. The table shows what each vendor's own help pages say about the built-in AI and who can switch it off.

ToolBuilt-in AI availability or defaultAdmin controls
AsanaIncluded on every paid planSuper admins and billing owners, for the whole organization or workspace
NotionPart of Business and Enterprise; Free and Plus get a limited number of trial responsesWorkspace owners control models, web search and credit limits
ClickUpIncluded with the new plans, not an add-onWorkspace owners and admins, for everyone or by role and person
monday.comAI features managed at account levelAccount admins, for the whole account; per role on Enterprise
Jira and ConfluenceRovo is available to everyone on Standard, Premium and EnterpriseOrganization admins, by blocking each app
TrelloAutomatically activated on Standard and Premium; on for Enterprise unless it opted outWorkspace admins, with the AI toggle
BreezeOffOff until an admin or the team owner turns it on

An off switch does not cover the same things in every tool:

  • Asana: its AI admin controls article says that once AI is disabled, AI experiences no longer appear or process data from your organization. Its AI partners include OpenAI, Anthropic, Google, Fireworks.ai and Recall.ai.
  • Jira: blocking Rovo in one Jira app leaves shared features such as AI search and chat running while any other Jira app on the site still has it. You have to block every Jira app on the site, and Atlassian notes the change does not take effect immediately.
  • ClickUp: admins can turn every AI feature off for the workspace. If you keep AI on, note that ClickUp's speech and music features can use ElevenLabs models, which ClickUp says may keep and train on data, and that they have their own switch.
  • Notion: the controls Notion documents narrow AI use, by model, web search and credits, rather than describe one switch that removes it. If that matters for a contract, ask Notion before you sign. Its AI plans and credits explain which plans include what.

If your team actually wants AI and only needs it governed, these defaults are fine. Compare the costs of AI project tools for the work you want them to do.

How do vendors use data?

Most say they do not train models on customer content, but Atlassian's data contribution settings need a separate check. From August 17, 2026, Atlassian uses data according to new data contribution settings, and the default depends on your highest plan.

Highest Atlassian planMetadataIn-app data (your content)
Free or StandardAlways contributed, cannot be changedOn by default, can be turned off
PremiumAlways contributed, cannot be changedOff by default
EnterpriseOn by default, can be turned offOff by default

For example, a ten-person team on Jira Standard contributes its in-app data unless an admin turns it off under Atlassian Administration, then Security, then Data contribution. Atlassian's data contribution article lists the defaults, and they apply to Jira, Confluence and Jira Service Management. Trello is not on that list. The Standard plan's wider pricing changes are covered in Atlassian's 2026 changes.

Asana says neither it nor its AI partners train on customer data. Notion says the same by default for itself and its providers. Breeze says its in-app AI never stores prompts or uses them for training. A vendor's promise covers the vendor; it does not cover an assistant a team member connects from outside.

Can staff connect outside assistants?

In most tools, team members can connect their own assistants. Whether an admin can block those connections varies by tool and plan. MCP connectors let someone sign in to the project tool from Claude, ChatGPT or another assistant, which can then read and change the work that person can reach. The data then goes to that assistant's provider under its terms, not the project tool's.

A padlocked iron garden gate, and further along the wall a side door where a young man walks in with a small robot carrying a clipboard
  • monday.com: MCP comes preinstalled on every account, and account admins can turn it off entirely with one toggle, allow only some assistants, or limit it to chosen workspaces. Its AI connectors article says an admin block applies regardless of individual authorization. This is the most complete control of the tools here.
  • Notion: on Enterprise, admins can approve or block each assistant that connects through Notion MCP. On other plans, members connect it themselves.
  • Trello: its MCP server is available to any user on any plan. Organization admins manage access only on Enterprise.
  • ClickUp: its MCP server is available on all plans, with daily call limits that depend on the plan.
  • Breeze: any person with a Breeze login can connect their own assistant, and there is no admin setting that blocks the connector for the team. The section below covers what an admin can do instead.

On many plans, no tool setting closes this route. A written team rule is the fallback, but it cannot block a connection, so check the connected apps list in each assistant when you review access.

What escapes the AI switch?

Breeze's MCP connector and live voice note transcription are not covered by its in-app AI switch. The built-in Breeze AI chat stays off until an admin enables it from the Features menu, as the built-in AI controls page explains.

Until an admin does that, the AI item does not appear in anyone's menu, and no project data is sent to the chat's model. When enabled, the chat uses Mistral's models. Breeze says prompts are used only to answer and are never stored or used for training.

The two separate routes work as follows:

  • Outside assistants: anyone with a Breeze login can connect Claude or ChatGPT to Breeze. The assistant acts as that person, with their permissions, and with write access it can create and edit tasks, move cards, change due dates, comment and log time. The in-app AI switch does not affect it, and there is no team setting that turns it off.
  • Voice note transcription: when someone records a voice note, Breeze transcribes it live using Mistral's speech model unless that person switches off Live transcript on the recording bar. It is a personal setting that starts on, not an admin one.

What an admin can do about the connector:

  • Limit what each person can reach: an assistant sees only the projects that person is a member of and can do no more than their role allows, so an observer's assistant is as limited as the observer. Admins control both in project access settings.
  • Remove access: taking someone off a project takes their assistant off it too. Each person can also disconnect Breeze in their assistant's connector settings.
  • Set the rule: for a client who forbids AI, the practical control is a written rule that nobody connects an assistant or records transcribed voice notes in that client's projects.

On Breeze's side, the help page says connector requests are logged for 14 days, nothing reached through the connector is used to train AI models, and search by meaning runs on Breeze's own servers rather than an outside AI provider. Those limits do not by themselves meet a ban on outside assistants. If the connector block matters to you, monday.com's admin toggle is stronger than anything Breeze has today.

Where Breeze does fit is a team that wants boards, lists, a calendar and time tracking with the AI chat left off unless it chooses to add it. It costs $9 per user per month billed yearly, or $10 billed monthly, with every feature included, and client users are free. It can import from Notion, Asana, ClickUp, monday.com and Trello. Compare alternatives to Notion against the same requirements.

What should client contracts cover?

Name built-in AI, vendor data use and outside assistants, and address transcription explicitly. A clause that says only "no AI tools" leaves the settings and responsibilities unclear. Have a lawyer write the final wording; these are the points it usually needs:

  • Built-in features: AI features in the tools that hold the client's data are switched off, with the setting named for each tool.
  • Vendor data use: the vendor does not use the client's content to improve its AI, with the data contribution or training setting recorded where one exists.
  • Outside assistants: nobody connects an AI assistant, browser extension or meeting bot to projects holding the client's data.
  • Transcription: no AI transcription of calls or voice notes about the client's work.
  • Subprocessors: the client can see the list of AI providers each tool uses, and gets notice before one is added.
  • Checks: who reviews the settings, how often, and what happens if a setting changes after a vendor update.

Then check each tool against the list before you sign. Where a tool cannot meet a point by setting, a rule plus a regular check has to cover it.

Which AI controls matter most?

Is there project management software without AI?
Few large tools leave AI out entirely, but some leave it off by default. Breeze's built-in AI chat stays off until an admin turns it on, but that switch does not cover its MCP connector or live voice note transcription. Asana, ClickUp, monday.com, Trello and Jira include AI on paid plans and let an admin switch it off.
Can I stop employees connecting ChatGPT or Claude to our project tool?
The available block depends on the tool and plan. monday.com admins can turn off all outside AI connections with one toggle, and Notion Enterprise admins can block individual assistants. Breeze has no admin block, and in Notion and Trello the block is limited to Enterprise plans, so a written team rule is the fallback, though it cannot block a connection.
Does Atlassian use Jira data for AI by default?
Atlassian turns in-app data contribution on by default for organizations whose highest plan is Free or Standard. This applies from August 17, 2026, and an admin can turn it off under Security, then Data contribution. Premium and Enterprise start with it off.