> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/team-collaboration/setup-teams-and-orgs.md).

# Set Up Nimbalyst Teams

Nimbalyst Teams has two layers. An **organization** holds the member roster, billing, messaging settings, and encryption. A **project** is one git repository attached to that organization, with its own shared documents and trackers. Nimbalyst uses the project's git remote as its identity, so teammates who open clones of the same repository connect to the same team project.

Setup lives in two places: **Settings** for your account and the current project, and the **organization management dialog** for everything organization-wide.

{% hint style="info" %}
Nimbalyst Teams is in **beta**. Expect bugs. Organizations are free during beta and will require a paid Nimbalyst Teams subscription after launch.
{% endhint %}

### Before you begin

Make sure that:

* You have opened the correct project in Nimbalyst.
* The project has a git remote named `origin` if you want automatic project matching.
* You are signed in to Nimbalyst under **Settings > Account > Accounts**.
* Teammates will sign in with the email addresses you invite.

### Create an organization

Your signed-in accounts and the organizations each one belongs to are listed under **Settings > Account > Accounts**. Use **New organization** here to start one, or **Manage** to open the management dialog for an existing one.

<figure><img src="/files/vm755pFgYzTpaaBPpwNB" alt="Settings, Account, Accounts, showing the signed-in email with its organizations, each with an Admin or Owner role badge, a Manage button, and a New organization button"><figcaption><p>Every organization your signed-in account belongs to, with your role in each.</p></figcaption></figure>

Each row shows your role, **Owner** or **Admin**, and how many projects the organization holds. The person who creates an organization becomes its owner. You can also **Add another account** and belong to organizations under more than one identity.

### Attach this project to an organization

Project-level sharing lives under **Settings > Project > Sharing**. This panel is where a repository becomes a team project.

<figure><img src="/files/SYAhnZ6xHi5eU4JEcfU6" alt="Settings, Project, Sharing, showing the Organization section with the signed-in account and the organization attachment controls"><figcaption><p>Settings > Project > Sharing attaches the current repository to an organization.</p></figcaption></figure>

To create a team from this project:

1. Open **Settings**.
2. Select **Project** at the top.
3. In the sidebar, select **Sharing**.
4. Click **Create Team**.
5. Confirm the team name and detected git remote. If you have more than one Nimbalyst account, choose the account that should own the team.
6. Click **Create Team**.

Nimbalyst creates the organization, registers this repository as its first project, and prepares the team's encryption.

If you already administer an organization, use **Add to an existing organization** instead of creating another one:

1. Select the organization.
2. Click **Add Project**.
3. Confirm that this workspace appears as a project under the organization.

Each project has its own tracker and document space. Projects in the same organization share the member roster, messaging settings, and encryption.

### Manage the organization

Organization administration is a dialog that opens in whatever window you are already in, rather than a fourth Settings scope. Open it any of these ways:

* **Organization switcher** in the navigation gutter, then **Manage organization…**.
* **Settings > Account > Accounts**, then **Manage** on the organization's row.
* The organization row in the **account menu** at the bottom of the navigation gutter.
* **Settings > Project > Sharing**, then **Open organization**, which lands on the **Projects** page.
* The pending-invitations row in the organization switcher, which lands on **Members**.

The dialog's sidebar holds **Members**, **Projects**, and **Settings**, plus **Billing** and **Danger zone** for owners and admins. Plain members do not see the last two.

**Window > Organization Messages** (**Cmd/Ctrl+Alt+O**) is a different surface. It opens the messaging window for rooms and direct messages, not the administration dialog.

#### Members and roles

**Members & Roles** carries a `beta` chip while roles and verification settle. Under **Members**, enter a teammate's email address and click **Invite**. The invite stays pending until that person joins. An owner or admin can revoke a pending invite, remove a member, or move a member between **Admin** and **Member**.

This page also shows identity fingerprints so teammates can verify one another. Compare fingerprints through a separate trusted channel before marking someone verified. A changed fingerprint means the member's device identity changed, so verify it again before trusting the new key. Owners and admins can re-share a team key when a verified member changes devices.

#### Projects

**Projects** lists every project in the organization, including ones you have not cloned locally.

<figure><img src="/files/3Ly2tNc2FZ6lSNNCIiuz" alt="The organization management dialog Projects page, listing a git-linked project with a Manage access button and a reserved Organization Space entry"><figcaption><p>Every project in the organization, whether or not you have a local clone.</p></figcaption></figure>

Use **Manage access** to control who can reach a project's shared documents and trackers. To add a project, open it in Nimbalyst and go to **Project Settings > Sharing > Add to an existing organization**. **Organization Space**, a shared area for documents and trackers that belong to the organization rather than to a single repository, is reserved for a later release.

#### Settings: messaging, security, and encryption

**Settings** covers organization-wide configuration. Members can view this page; only owners and admins can change it.

<figure><img src="/files/haFavr4lkYlhBpAkZoy8" alt="The organization management dialog Settings page, showing the organization name with a Rename action, Messaging toggles for Rooms and Direct messages, a who-can-create-rooms selector, and a Security panel reading Encrypted by Nimbalyst with encryption active"><figcaption><p>Rename the organization, control built-in messaging, and check encryption status.</p></figcaption></figure>

* **Organization:** Rename the organization. The owner's email address is shown beneath it.
* **Messaging:** Turn **Rooms** and **Direct messages** off for organizations that chat elsewhere. The Inbox, document comments, and tracker comments are unaffected. **Who can create rooms** offers **Any member** or **Organization admins only**, and is unavailable while Rooms is off.
* **Security:** Team data is encrypted in transit and at rest with keys managed by Nimbalyst. This is separate from personal sync encryption, whose keys remain only on your devices.

**Billing** and **Danger zone** round out the dialog. Details on encryption, data isolation, and SOC 2 are on the [security page](https://nimbalyst.com/features/security/).

### Join an invited team

The invited person should:

1. Sign in to Nimbalyst with the invited email address.
2. Open a clone of the team's repository in Nimbalyst.
3. Open **Settings > Project > Sharing**.
4. Click **Join Team** on the invitation card.

Because the repository remote matches the team project, the shared documents and trackers become available once the invitation is accepted and the encryption key is ready.

If the invite does not appear, confirm the signed-in email address and the repository's `origin` remote first.

### Use multiple accounts

Add or reconnect accounts under **Settings > Account > Accounts**, then switch between them from the account menu in the navigation footer.

When you create an organization, add a project to one, or create a shared link, Nimbalyst lets you choose which signed-in account owns that action. Organization membership and project access continue to use that account even when another account is selected for personal mobile sync.

If an invitation or team project is missing, first switch to the account whose email address received the invitation.

### Which scope does what

| You want to…                                              | Go to                              |
| --------------------------------------------------------- | ---------------------------------- |
| Sign in, add an account, or start an organization         | **Settings > Account > Accounts**  |
| Attach this repository to an organization, or join a team | **Settings > Project > Sharing**   |
| Choose which tracker types sync to the team               | **Settings > Project > Trackers**  |
| Invite people, set roles, verify fingerprints             | **Organization dialog > Members**  |
| Manage project access across the organization             | **Organization dialog > Projects** |
| Rename the org, control messaging, check encryption       | **Organization dialog > Settings** |
| Chat in rooms and direct messages                         | **Window > Organization Messages** |

Team content is authorized with the active team membership. Personal session and mobile sync use a separate personal identity and do not grant access to team documents or trackers. See [Application, Account, and Project Settings](/setup-nimbalyst/settings-scopes.md) for the complete settings model.

### Start collaborating

After the team is connected:

* Open **Collaboration** mode to create and organize shared documents.
* Right-click a supported local file and choose **Share to Team**.
* Open **Trackers** to share hybrid items or work in tracker types configured as shared.

Continue with [Collaborative Documents](/team-collaboration/documents.md) and [Collaborative Trackers](/team-collaboration/trackers.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nimbalyst.com/team-collaboration/setup-teams-and-orgs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.