Credentials visibility issue: Owner sees Member's credential in Node, but cannot see their own (Project Scope?)

Questions
1

Hi everyone,

I’m facing a strange behavior regarding credentials visibility and I suspect it might be related to Project Scopes, but I need confirmation.

Setup:

  • n8n Self-hosted (Version: 1.121.3

  • User A: Owner

  • User B: Member

The Issue:
I am logged in as Owner.

  1. I have a Gmail credential created by me.

  2. The Member (User B) has a Gmail credential created by them.

  3. When I open a Workflow and add a Gmail Node:

    • The dropdown SHOWS the Member’s credential.

    • The dropdown DOES NOT SHOW my own credential.

Question:
Is it possible that my credential is “stuck” in a Personal Project while the workflow is in a Team Project? How exactly does the Node dropdown filter credentials based on the Owner’s view vs Project scope?

1 Like
3

yeah this is 100% a project scope thing - your credential is in a different project than the workflow youre working on

quick fix:

1. go to Settings → Credentials and find your gmail credential

2. click it and check which project its under (probably Personal or a different team project)

3. either move the credential to the same project as the workflow, OR share it with that project

the workflow can only see credentials that are in the same project or explicitly shared with it. the member’s credential shows up because its already in that project scope

lmk if moving it fixes the visibility