> 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.md).

# Set Up a Team

Set up the team from the project you want to collaborate on. 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.

> **Free alpha:** Nimbalyst Teams is free during the alpha. Alpha features may have bugs or change before launch. Teams will require a paid subscription after launch; final pricing has not been announced. [Join the waitlist](https://nimbalyst.com/waitlist/) for launch and pricing updates.

The setup controls below appear when Teams early access is enabled for your account.

### 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.

Current availability and account access are shown in Team settings.

### Create a team for 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**.

The person who creates the team becomes an admin. Nimbalyst creates the organization, registers this repository as its first project, and prepares the team's encryption.

### Add this project to an existing organization

If you already administer an organization, use **Settings > Project > Sharing > Add to an existing organization** instead of creating another team.

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 and organization encryption settings.

### Invite teammates

Owners and admins invite members from the dedicated organization window:

1. Open the organization switcher or choose **Window > Organization Manager (Alpha)**.
2. Choose the organization if you belong to more than one.
3. Open **Members & Roles** or **Security & Projects**.
4. Under **Members**, enter the person's email address and click **Invite**.
5. The invite appears as pending until that person joins.

An owner or admin can revoke a pending invite, remove a member, or change a member between **Admin** and **Member**.

### 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 after the invitation is accepted and the encryption key is ready.

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

### Choose the right settings scope

Nimbalyst separates application, account, project, and organization administration:

* **Account > Accounts**: sign in, add accounts, reconnect, and choose the personal sync identity.
* **Account > Mobile App**: select projects and documents for personal mobile sync.
* **Project > Sharing**: create a team, join one, add the current repository to an organization, or see which organization project this workspace uses.
* **Organization window > Members & Roles**: manage the team roster and roles.
* **Organization window > Security & Projects**: manage linked projects, team encryption, identity fingerprints, project moves, and organization-level administration.

The organization switcher in the navigation gutter appears after you belong to a team. Use it to open the settings for another organization.

See [Application, Account, and Project Settings](/setup-nimbalyst/settings-scopes.md) for the complete settings model.

### 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.

### Verify members and encryption

Team settings shows identity fingerprints for members so teammates can verify one another.

* Compare fingerprints with teammates through a separate trusted channel before marking them verified.
* A changed fingerprint is a warning that the member's device identity changed. Verify it again before trusting the new key.
* Owners and admins can re-share a team key when a verified member changes devices.
* **Security & encryption** shows the team's encryption status. Shared documents, Trackers, and tasks flow through Nimbalyst's Cloudflare sync service and are encrypted in transit and at rest, with data isolated per team.

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.

Nimbalyst-hosted Teams uses server-managed encryption keys. Team data is encrypted but is not zero-knowledge; personal device sync remains end-to-end encrypted with keys that stay on your devices.

### 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.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.
