---
title: Organizations & Teams
description: >-
  Create organizations, invite team members, manage roles, and collaborate on
  drug discovery projects.
tags:
  - organizations
  - teams
  - collaboration
  - roles
  - members
---

  intermediate

The ivybloom CLI is the scriptable surface for the platform, and organizations are how you enable multi-user collaboration — creating teams, inviting members, and managing roles so projects, campaigns, and job results are shared across a group. Reach for these commands when scripted work needs to run in a shared, multi-user context rather than a single individual account. They set the boundary within which your automated pipelines and their results are shared; for the full command surface, see the [CLI overview](/docs/cli).

## Organizations & Teams

Create organizations, invite team members, manage roles, and collaborate on drug discovery projects.

---

## Overview

Organizations enable multi-user collaboration on .bloom*. Members share projects, campaigns, and job results within an organization while maintaining individual accounts.

---

## Creating an Organization

```bash
ivybloom org create --name "My Lab" --description "Computational chemistry team"
```

The creator becomes the organization owner.

---

## Listing Organizations

```bash
ivybloom org list
```

Shows all organizations you belong to with your role in each.

---

## Organization Details

```bash
ivybloom org info ORG_ID
```

View organization name, description, member count, and settings.

### Update Organization

```bash
ivybloom org update ORG_ID --name "New Name" --description "Updated description"
```

---

## Member Management

### List Members

```bash
ivybloom org members ORG_ID
```

Shows all members with their roles and join dates.

### Invite Members

```bash
ivybloom org invite ORG_ID --email colleague@example.com
ivybloom org invite ORG_ID --email colleague@example.com --role admin
```

The invited user receives an email with a link to accept.

### View Pending Invitations

```bash
ivybloom org invitations ORG_ID
```

### Respond to Invitations

```bash
# Accept
ivybloom org respond INVITATION_ID --action accept

# Decline
ivybloom org respond INVITATION_ID --action decline
```

### Remove Members

```bash
ivybloom org remove-member ORG_ID USER_ID
```

> Removing a member immediately revokes their access to all organization resources.

---

## Roles & Permissions

### Available Roles

| Role | Projects | Jobs | Members | Billing | Settings |
|------|----------|------|---------|---------|----------|
| **Owner** | Full | Full | Full | Full | Full |
| **Admin** | Full | Full | Invite/Remove | View | Edit |
| **Member** | Create/Edit | Submit/View | View | - | - |
| **Viewer** | View | View | View | - | - |

### Set Member Role

```bash
ivybloom org set-role ORG_ID USER_ID --role admin
```

> Only owners can promote members to admin or transfer ownership.

---

## Shared Workflows

### Shared Projects

Organization members can access shared projects:

```bash
# Create a project
ivybloom projects init "Lead Optimization"

# List the projects you can see, including organization projects
ivybloom projects list
```

The CLI has no `--org` flag on project or campaign commands. Organization context comes from the signed-in account.

### Shared Campaigns

Campaigns created within an organization are visible to all members with appropriate roles:

```bash
ivybloom campaigns list
```

### Result Sharing

All jobs submitted to organization projects are visible to team members. Results and artifacts can be downloaded by any member with view access.

---

## Team API Keys

Create an API key for a shared CI/CD pipeline. Keys belong to the user who creates them; the CLI has no organization option on `apikeys create`:

```bash
ivybloom apikeys create --name "team-ci-key" --scope read_write
```

> Use separate API keys for each CI/CD environment (development, staging, production) and rotate them regularly. See [API Keys](/docs/cli/api-keys) for scope options.

---

## Read next

- [API Keys](/docs/cli/api-keys) — Team authentication and scoped keys
- [Billing & Credits](/docs/cli/billing) — Organization billing and usage
- [Sessions & Checkpoints](/docs/cli/sessions) — Collaborative session management
- [Commands Reference](/docs/cli/commands) — Full command documentation