> 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/teams-tutorial.md). # Nimbalyst Teams: Step by Step Seven steps from a solo workspace to a team working in the same trackers, the same documents, and the same files as their coding agents. Every screen below is the product as it ships. Watch the whole walkthrough in under three minutes, or read the steps below. {% embed url="" %} ## Step 1. Sign in to Nimbalyst Open the user menu at the bottom of the left rail and choose **Sign in**.

The Nimbalyst user menu open, showing Application Settings, Project Settings, No organization, and Sign in — The user menu at the bottom of the left rail.

Sign in with Google or with a magic link sent to your email address. Signing in is what connects this copy of Nimbalyst to a team.

The Account tab in Nimbalyst Settings, showing Continue with Google and an email field for a magic link — Sign in from Settings, under Account.

## Step 2. Create your organization From that same menu, choose **Set up** next to **No organization**.

The user menu with the No organization row highlighted and a Set up action beside it — Set up an organization from the user menu.

Name your organization. Everyone you invite sees this name, and you can change it later.

The New organization dialog on its Name step, with an organization name typed in and the owner's address below the field — Step one of three: name the organization.

Then invite your teammates by email. They join as members, and you can change roles afterwards.

The New organization dialog on its Invite step, with a teammate's email address entered — Step two of three: invite the team.

Everyone you add appears in the organization's member list, where you can change a role or invite more people at any time.

The organization management dialog listing team members with their email addresses and roles, and an invite field at the bottom — The member list for your organization.

## Step 3. Your teammate receives an invite email They receive an email with one button. There is no account to create first.

The invitation email, with an explanation of Nimbalyst and a Join button — The invitation email your teammate receives.

## Step 4. They accept and land in the team Clicking through accepts the invitation and puts them in the organization. From there they can open the team in the desktop app, or keep working in the browser.

The confirmation screen after accepting an invitation, offering to open the desktop app or continue in the browser — Accepted, and in the team.

## Step 5. Working collaboratively in trackers Switch to **Tracker** mode. With a team, the left navigation splits into two groups. The top group belongs to the organization and everyone in it sees the same items. The bottom group stays on your machine.

The tracker sidebar split into a Northwind section marked Shared with 5 people and a Personal section marked Local only — The team's trackers lead. Yours stay local.

Every tracker opens as a grid you can edit in place. Press **Cmd+Shift+N** anywhere in Nimbalyst to launch an agent session against whatever you are looking at, without leaving the board.

Open an item and it expands into a full document the team writes together, with its own agent chat alongside.

A tracker item expanded to full width with a written body and a Chat about this item panel on the right — An item's body is a document, not a text field.

Put a file reference on its own line in that body and it becomes a live embed. Anyone with access can edit it in place, or open it in its own editor.

A tracker item body containing two live embeds, an Excalidraw diagram and a UI mockup, each with its path and an Open action — Embedded files render live inside the item.

Link your own agent sessions and the files they touched to an item, so the work and the record of it stay together.

A tracker item detail panel showing a Sessions section with Link Existing and Launch Session actions — Link an existing session, or launch a new one from the item.

## Step 6. Working collaboratively in documents Right click any file in your project and choose **Share to Team**. Nimbalyst scans the file for embedded files and offers to share those alongside it, so your teammates do not open the document and find empty placeholders.

The file tree context menu open on a markdown file, showing the Share to Team action — Any project file can become a shared document.

**Shared Docs** holds every shared document and folder in one place. A blue dot marks anything changed since you last opened it.

The shared documents space with a folder tree on the left and a table of shared documents with authors, last edited times, and unread dots — One space for everything the organization shares.

Star the documents you work in every day and the **Favorites** filter brings them straight back.

The shared documents space filtered to Favorites, showing a single starred document — Favorites, one click away.

Open a shared document and you are editing the same copy as everyone else, with a labelled cursor for each person. Each teammate's locally running coding agent works in that same document.

A shared launch plan open in Nimbalyst with a teammate's labelled cursor in the text and an agent prompt staged in the chat — People and their agents, in one shared copy.

Select a passage to leave a comment, mention someone with `@`, and reply in the thread. Comments live with the document, so they follow it everywhere it is opened.

A comment thread on a highlighted passage of a shared document, with a reply below the first comment — Comments and replies attach to the passage they are about.

Anything addressed to you shows a badge in the top right corner of the window.

The top-right toolbar cluster in Nimbalyst with an unread count badge on the inbox button — The unread badge, top right.

Open it for a single list of every mention, comment, and message waiting on you, each linked to the document it came from.

The team inbox listing mentions, comments, and messages with the document each one came from — Every mention, comment, and message in one list.

## Step 7. Teammates can work in the browser Someone without the desktop app opens [console.nimbalyst.com](https://console.nimbalyst.com) and reads, writes, and comments on the same shared documents. People on the desktop app and people in the browser work side by side on the same files.

The Nimbalyst web console showing the same shared document tree and table in a browser — The same shared space, in a browser.

See [Web Console](/team-collaboration/web-console.md) for what the browser supports. ## Where to go next * [Team Collaboration Overview](/team-collaboration/overview.md) * [Collaborative Documents](/team-collaboration/documents.md) * [Collaborative Trackers](/team-collaboration/trackers.md) * [Set Up Nimbalyst Teams](/team-collaboration/setup-teams-and-orgs.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/teams-tutorial.md?ask=&goal= ``` `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.