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

# Organizations

> Top-level Ionworks workspace containing projects, cells, models, and members with shared organization-level resources and roles

An **Organization** is the top-level container in Ionworks. It represents your team's workspace where all your projects, data, and members are managed.

## Organization Structure

```
Organization
├── Models
└── Projects
    ├── Cell Specifications
    │   └── Cell Instances → Measurements → Analyses
    ├── Materials → Property Datasets
    ├── Parameterized Models
    ├── Protocols
    ├── Studies → Simulations
    ├── Pipelines
    └── Optimizations
```

## Key Concepts

### Central Workspace

Your organization is the central hub for all your work. Every [Project](/core-concepts/projects-studies) and [Model](/build/models) belongs to your organization, and every [Cell Specification](/core-concepts/cells) and [Parameterized Model](/build/parameterized-models) belongs to a project inside it.

### Shared Resources

* **Models** are available to all team members across every project.
* **Cell Specifications** and **Parameterized Models** are scoped to a single project. To reuse a cell design in another project, create a new Cell Specification in that project. The exception is a Quick model, which has no cell specification and is shared across the organization.
* **Sites** are organization-wide test facilities. Their **Cyclers** and **Channels** belong to both a site and a project, so they sit outside the tree above rather than under one parent — see [Equipment](/operate/equipment).

### Team Collaboration

* Invite team members to your organization
* Manage access through roles at two levels — organization and project
* Give each member the right access per project, rather than all-or-nothing

### Roles

Access is granted at two levels, and a member needs both: organization
membership says they belong, and a project role says what they can do inside a
given project.

| Level        | Roles                                                          | What it controls                                                                                          |
| ------------ | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Organization | **Admin**, **Member**                                          | Belonging to the organization. Admins additionally manage members, branding, and organization settings.   |
| Project      | **Project Admin**, **Project Contributor**, **Project Viewer** | What the member can do in that project — view only, create and edit, or also manage the project's access. |

Organization membership is the baseline rather than a grant of access: being a
Member means you belong to the organization, and your project role decides what
you can see and change in each project. A **Project Viewer** can read a
project's cells, models, and results but cannot create, edit, or delete
anything — write actions simply aren't offered.

## Managing Members

Organization admins can invite new members, change roles, deactivate access, or remove members entirely from the organization's **Members** settings.

### Adding a Member

Add a member from the Members tab by entering their email address. Email
matching is **case-insensitive**, so `Alice@example.com` and `alice@example.com`
resolve to the same person — you won't accidentally create a duplicate
membership by typing a differently-cased address.

The add-by-email flow surfaces two distinct outcomes so you know what happened:

* **Newly invited user** — the email doesn't yet belong to an Ionworks account.
  An invitation email is sent so they can create an account and join the
  organization.
* **Already registered user** — the email belongs to an existing Ionworks user.
  They're added to the organization immediately and can sign in with their
  existing credentials.

### Resending Invites and Password Resets

From the **Members** tab, an admin can:

* **Resend an invite** to a member who hasn't accepted their invitation yet —
  useful when the original email was missed or expired.
* **Send a password reset** to any member — a self-service reset link is
  emailed to them without touching their account otherwise.

Both actions live in the row-level menu next to each member in the list. They
send the email only — neither changes the member's role or membership, and
neither writes an activity-log entry, so they leave no record in the
organization's history.

### Deactivating a Member

Deactivating a member blocks their access to the organization while keeping their membership record and role intact. This is the recommended way to temporarily revoke access — for example when someone changes teams, goes on leave, or needs their access paused during an audit — without losing their assignments or history.

* **Deactivated members** cannot sign in to the organization. If it is their active organization, they see an *Access deactivated* screen and can switch to another organization they belong to, or contact support.
* Their **role and membership are preserved**, so reactivating restores their previous access with no reconfiguration.
* Deactivated members appear in the members list with a **Deactivated** badge.

To deactivate a member:

1. Open **Organization settings → Members**.
2. Find the member in the list and click **Deactivate**.
3. Confirm in the dialog. The member's role is preserved and they can be reactivated at any time.

To reactivate a member, click **Activate** next to their name in the members list.

<Note>
  Admins cannot deactivate their own membership, and the organization's last active admin cannot be deactivated. Use **Remove** instead if you want to end a member's association with the organization entirely — this deletes the membership row and any role assignment.
</Note>

## Branding

An organization can show its own logo and name in the sidebar instead of the
default Ionworks branding, from **Organization settings → Branding**. Only
organization admins can change it; everyone in the organization sees the result.

* **Name** — the display name shown beside the logo, up to 120 characters. Leave
  it unset to show the organization's own name.
* **Logo** — a PNG, JPEG, WebP, or SVG image up to 2 MB. Remove it at any time to
  fall back to the default.

## Next Steps

* Create a [Project](/core-concepts/projects-studies) to organize your work
* Define [Cell Specifications](/core-concepts/cells) for your batteries
* Set up [Models](/build/models) for simulation