# n8n lets builders use personal credentials inside team projects

> The 2.46 release adds personal credentials in shared projects, while run and publish permissions continue to follow the acting user.

Canonical: https://stacktak.com/news/n8n-personal-credentials-team-projects-beta
Author: Stacktak Editorial
Published: 2026-10-29T14:00:00Z
Modified: 2026-10-30T13:47:45Z

A shared workflow does not always need a shared account connection. n8n’s [October 27 changelog entry](https://docs.n8n.io/changelog) introduces personal credentials inside team projects with version 2.46.0, letting builders use their own connection without first sharing it with the project.

That does not give every teammate permission to run it. Someone without access can see the credential’s name and owner, but cannot execute or publish the workflow using it. They can switch to their own credential or request access.

## The person running the workflow matters

The [credential guide](https://docs.n8n.io/administer/manage-credentials/use-personal-credentials-in-projects) distinguishes manual runs, which act as the person pressing Execute, from triggered runs, which act as the last publisher. Project-held credentials remain the option for connections the whole project needs. Agents currently use project credentials only.

There is a release-track condition too. At publication, n8n’s changelog places the 2.46 series on the beta track and the stable release on 2.45. A documented capability should not be assumed to exist on an older production instance.

The practical handoff is now more explicit: share the workflow, then decide separately who may use its connections. Before republishing a team automation, confirm which identity will run the scheduled or event-triggered work.

## Sources

[n8n — October 27 release and current tracks](https://docs.n8n.io/changelog) · [Personal credentials in projects](https://docs.n8n.io/administer/manage-credentials/use-personal-credentials-in-projects)