Notion adds Slack access controls and admin limits for Custom Agents

Notion moved Custom Agents closer to real workplace infrastructure this month, first by letting them read and reply in private Slack channels, then by adding the kind of controls enterprise buyers ask for after the demo ends. The company said the Slack access was limited to private channels explicitly invited by the workspace, a narrow boundary that makes the permission model as important as the agent itself.

Two weeks later, Notion said teams had created more than one million Custom Agents since the beta launched two months earlier. That scale helps explain the next release: admin controls for who can create agents, per-agent credit limits, workspace-wide credit limits, and dashboards that show usage and spend. In practice, Notion is signaling that the next phase of agent adoption will be governed less by feature curiosity and more by budget discipline and access control.

The company’s help center fills in the operational picture. Workspace admins can manage Custom Agents through an Agent Directory, creation controls, content search, audit logs, AI analytics, and ownership transfer tools. Notion also says that sharing a Custom Agent gives users access to everything the agent can see, a detail that turns permissioning into a frontline security issue rather than a back-office setting. Custom Agents can run on triggers and schedules, be @mentioned in pages and comments, and take actions across connected tools. Slack access requires an admin to connect the Slack AI connector first, and Notion says the feature is available on Business and Enterprise plans, with Notion credits for Custom Agents sold as a recurring add-on on both tiers.

For monday.com employees, the message is hard to miss. In late April and early May, monday.com announced a dedicated path for AI agents on its platform, while its support docs said admins could manage AI permissions and monitor credit usage through governance tools. Enterprise customers can set credit limits at the account, feature, and user levels. That puts monday.com in the same race Notion is running: not just to make agents useful, but to make them safe to deploy, easy to oversee, and predictable to fund.

That shift matters across product, engineering, and sales. Product teams are now building toward approvals, logs, and rollback paths as much as toward task completion. Engineers are being asked to make agents behave inside quotas instead of only perform well in tests. Sales teams are learning that buyers want to know how quickly a workspace can contain an agent that goes off-script, who can create one in the first place, and how much the rollout will cost if usage jumps overnight. The competitive edge is moving from capability alone to control, and Notion just made that visible.