> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noclick.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Credentials and other people

> How collaborators run your workflows without seeing your secrets, and how to share a credential directly.

## Collaborators on a shared workflow

When you [share a workflow](/collaboration/sharing) for editing, your collaborators can run it without connecting their own accounts. Nodes that use your credentials resolve them as you, the workflow owner, at run time.

What collaborators see and get:

* The node shows the credential's name with an owner note: "Owned by \[you]. It's shared with this flow."
* The secret itself is never shown, copied, or added to their account; values are only decrypted server-side when the node executes.
* Edit, share, and delete controls are hidden for them, and the backend rejects those actions from anyone but the owner.

<Frame caption="A collaborator's view of a node using the owner's credential.">
  <img src="https://mintcdn.com/noclickinc/M99Xyd8Ho6Jf17gu/images/credentials/sharing-1.png?fit=max&auto=format&n=M99Xyd8Ho6Jf17gu&q=85&s=7a14a9cb3fdeb55057b2b4ff58169716" alt="Node credential with the owned-by tag" width="2070" height="274" data-path="images/credentials/sharing-1.png" />
</Frame>

<Note>
  This works one workflow at a time. Sharing a workflow never grants access to your credentials in the collaborator's other workflows.
</Note>

## Sharing a credential directly

You can also share a credential itself, so someone can use it in their own workflows:

1. Open **Settings → Credentials** and click the share icon on a credential you own (or use the share icon next to it in any node's credential picker).
2. Add people by email, or share with an organization to cover all its members. Each recipient gets **Can view** or **Can edit** permission.
3. Recipients see it under **Shared With Me** in their own Settings → Credentials and can select it on nodes like any other credential.

You can change a recipient's permission or remove them at any time by expanding the credential's row; recipients can likewise remove a shared credential from their list.

## Organization credentials

Inside an organization, the **Organization** tab in Settings → Credentials collects credentials owned by or shared with the org. These are available to all members, and they count against the organization's plan limit rather than anyone's personal cap. Runs of organization workflows bill the org owner's credit pool regardless of who runs them; see [Organizations](/collaboration/organizations).

## Next steps

<CardGroup cols={2}>
  <Card title="Workflow sharing" href="/collaboration/sharing">
    Invite links, view/edit access, and public links.
  </Card>

  <Card title="How credentials are protected" href="/credentials/security">
    Encryption at rest and what other users can see.
  </Card>
</CardGroup>