# Understanding Organizations
Source: https://docs.chain.link/chainlink-platform/understanding-organizations
Last Updated: 2026-10-15

> For the complete documentation index, see [llms.txt](/llms.txt).

## What is an organization?

A Chainlink Platform organization is a collaborative workspace that allows multiple team members to deploy, manage, and monitor workflows together. When you create an account, you either start a new organization (becoming the *Owner*) or join an existing one (becoming a *Member*).

An organization serves as a container for:

- **Multiple team members** with roles assigned per product
- **Linked wallet addresses** from all team members
- **Deployed workflows** visible to all organization members
- **Shared monitoring** of workflow executions and activity
- **API keys** for programmatic access to products

Organizations enable teams to collaborate on workflows while maintaining individual control over their own wallet addresses and secrets.

## Organization structure

### Single Owner model

Every organization has exactly **one Owner**: the person who first created the organization account. The Owner role:

- Cannot be transferred or changed
- Includes every permission for every product
- Can invite new members to join
- Can link wallet addresses and deploy workflows

### Multiple Members

Members are users invited to join the organization. Each member:

- Joins automatically after accepting the invitation and creating their account
- Has a role for each product, such as CRE, ACE, or CRE Connect
- Can link their own wallet addresses to the organization
- Can deploy and manage their own workflows, depending on their roles
- Views all organization workflows in the shared dashboard

### Shared visibility

All organization members can:

1. **View linked wallet keys** - Use `cre account list-key` to see all addresses linked to the organization by any member
2. **Monitor all workflows** - Access [app.chain.link/cre/workflows](https://app.chain.link/cre/workflows) to view:
   - All deployed workflows across the organization
   - Recent execution history
   - Workflow status (Active, Paused, Pending)
   - Execution success/failure metrics
   - Activity graphs and trends

## Organization roles

Chainlink Platform uses role-based access control (RBAC). Each member has a role for each product, and each role determines what the member can do with that product. For example, a member can be an ACE Admin and a CRE Viewer at the same time. A member with no role for a product cannot access that product.

The Owner role includes every permission for every product. See [RBAC](/chainlink-platform/rbac) for the full list of roles and what each role can do.

**Key points:**

- There is only one Owner per organization
- Owner permissions cannot be transferred
- Members with the invite permission, such as Platform Admins and the Owner, can invite new members
- Members automatically join after accepting the invitation and creating an account

## API keys

Organizations can create API keys for programmatic access to products, such as the CRE CLI and the ACE APIs. A single API key can include permissions for multiple products. See [API Keys](/chainlink-platform/api-keys) to learn how to create and manage API keys.

## Learn more

- **[RBAC](/chainlink-platform/rbac)** - Learn about member roles and what each role can do
- **[API Keys](/chainlink-platform/api-keys)** - Create and manage API keys for programmatic access
- **[Inviting Team Members](/chainlink-platform/inviting-team-members)** - How members with the invite permission can add members to the organization
- **[Linking Wallet Keys](/cre/guides/operations/linking-wallet-keys)** - How to link your wallet address to deploy workflows
- **[Creating an Account](/chainlink-platform/creating-an-account)** - How to create an account and join or create an organization
- **[Deploying Workflows](/cre/guides/operations/deploying-workflows)** - Deploy your first workflow after linking a key