Documentation Home

Understanding Organizations

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
  • Product resources such as CRE workflows, ACE policies, and CRE Connect channels, visible to members according to their roles
  • 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 product resources, such as CRE workflows, when their role for that product includes view access

Shared visibility

Organization resources are shared across the whole organization, but each member sees only what their roles permit:

  1. Linked wallet addresses - Members whose role includes platform:owner_address:read, which every Platform role (Admin, User) includes, can see all addresses linked to the organization by any member. The cre account list-key CLI command lists the same addresses.
  2. CRE workflows - Members with any CRE role (Admin, Developer, Viewer) can view all CRE workflows in the organization at app.chain.link/cre/workflows, including:
    • Recent execution history
    • Workflow status (Active, Paused, Pending)
    • Execution success and failure metrics
    • Activity graphs and trends
  3. Other products - ACE, CRE Connect, Data Streams, and Agent Gateway resources follow the same model: a member with a role for the product can view its resources, and a member without a role for a product cannot access it.

See RBAC for the permissions each role includes.

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 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 to learn how to create and manage API keys.

Learn more

Get the latest Chainlink content straight to your inbox.