Share Notion Workers before team agents fork the same automation

Confirmed: Notion added team sharing for Notion Workers on July 9, 2026. The change lets teammates connect an existing Worker to their own Custom Agents, or receive full access to improve it and adapt it to another workflow. The useful shift is operational: a Salesforce, support, CRM, or reporting Worker no longer has to stay trapped in the account of the teammate who built it.

What changed

Notion Workers can now be shared across a team from the Developer Portal. Notion describes two permission levels: Can connect, which lets teammates use a Worker with their own Custom Agents, and Full access, which lets them improve the Worker or apply it to a new problem.

The release builds on Notion's broader 2026 move toward workspace agents, Workers, and developer automation. In that context, Worker sharing is the piece that makes reusable agent tools easier to govern across a workspace instead of rebuilding them for each team.

Key takeaways

• Notion Workers can now be reused by teammates instead of staying tied to one builder.
• Can connect is the safer default when a team only needs to attach a Worker to Custom Agents.
• Full access should be reserved for teammates who need to edit, extend, or repurpose the Worker.
• The change matters most for shared business systems such as Salesforce, support desks, analytics, finance, and project operations.
• Admins should check Worker usage, credits, and audit trails before letting many agents call the same automation.

Availability and access

Notion says teams can start from Settings -> Connections -> Go to developer portal, or go directly to app.notion.com/developers. The release note does not say that every plan gets the same Worker access, so teams should verify plan eligibility inside their own workspace before designing around it.

Independent Notion ecosystem coverage notes that Workers are available for Business plan workspaces and above, with Worker-related billing tied to Notion's credit system after an initial free period. Treat those details as implementation context, not a substitute for checking your own admin console and current Notion docs.

Practical LinkLoot angle

This is a good moment to stop making every Custom Agent carry its own copy of the same automation. If one Worker enriches company records, checks duplicate CRM entries, pulls support status, or syncs external data into Notion, sharing lets that Worker become a governed team asset.

The practical workflow is simple: name the Worker by job, document what data it touches, give most teammates Can connect, and reserve Full access for the automation owner. That keeps agent setup fast without turning every workspace member into an accidental maintainer.

Teams building agent workflows can pair this with LinkLoot's AI workflow automation guide at /guides/ai-workflow-automation when deciding which steps belong in code, which belong in an agent, and which should stay manual until permissions are clear.

What to verify before you act

• Open the Developer Portal and confirm your workspace plan can create and share Workers.
• Check whether Can connect is enough before granting Full access.
• Review what databases, integrations, and external APIs the Worker can reach.
• Check Notion credits or usage reporting before connecting the Worker to high-volume agents.
• Confirm audit-log visibility if the Worker can change records, send messages, or touch regulated data.

Source check

Confirmed by: Notion's July 9 release note states that Workers can be shared across a team, that teammates can connect shared Workers to Custom Agents, and that Can connect and Full access are the two named access levels.

Context: Matthias Frank's Notion Workers guide gives practical implementation context around Workers, triggers, costs, and when code should handle deterministic work. Releasebot independently lists the July 9 Worker-sharing entry in its Notion update timeline.