> 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/web-console.md). # Web Console (console.nimbalyst.com) The Nimbalyst Web Console at [console.nimbalyst.com](https://console.nimbalyst.com) opens your team's shared documents in a browser. No install, no local setup, and the same collaboration service and permissions as the desktop app. It exists so the people who need to read and respond to your work do not need to become Nimbalyst users first. Write a plan in the desktop app, share it with your team, and a teammate can open the link, follow your live edits, and leave comments from any browser. {% hint style="info" %} The console is part of Nimbalyst Teams, which is in **beta**. Expect bugs. Organizations are free during beta and will require a paid Nimbalyst Teams subscription after launch. {% endhint %} They can edit it too. Editing runs in both directions: a teammate with edit access types straight into the same document you are in, and their changes land in your desktop app as they make them. You each see the other's cursor while you work.
A shared markdown plan open in the browser editor, with a teammate's labeled cursor in the document, a comments button showing four threads, and an Open in desktop link

A shared plan open in a browser, with a teammate editing alongside you.

### What you can do in a browser * **Open shared documents.** Browse your organization's shared document tree, folders, and projects. * **Edit live.** Shared markdown documents are fully editable, with everyone's changes syncing in real time. * **See who else is here.** Live labeled cursors show each teammate editing alongside you, colored per person. * **Comment on the text.** Select a passage, add a comment, reply, resolve, and mention teammates with `@`. * **Manage your organization.** Billing, roles, invitations, security posture, and organization lifecycle. The browser is a companion to the desktop app rather than a replacement for it. See [What the browser cannot do](#what-the-browser-cannot-do) for the specifics. ### Signing in The console uses the same account as the desktop app. Two ways in: 1. **Continue with email** sends a magic link to your work address. 2. **Continue with Google** uses your connected Google identity.
The Nimbalyst Web Console sign-in screen, with a work email field and a Continue with Google button

Sign in with the account connected to your organization.

If your account belongs to more than one organization, you choose which one to open after signing in. You can switch organizations later from the profile menu at the bottom of the left navigation, without signing in again. Browser sessions last seven days and are scoped to one signed-in account. If you follow a link to a document while signed out, the console remembers where you were headed and returns you there after you sign in.
The console sign-in screen showing an alert reading: Your session is not active. Sign in to continue to this organization link.

Following a shared link while signed out preserves your destination.

### Accepting an invitation When an organization admin invites you by email, the invitation link brings you to the console and accepts your membership. Because the full Nimbalyst experience lives in the desktop app, the console then offers to open Nimbalyst for you, with a download link if you do not have it yet. **Continue in the browser instead** takes you to the shared documents. ### Working in shared documents The left navigation has two modes: **Shared Docs** and **Organization**.
The web console listing an organization's shared documents in a table with Name, Type, Created by, Last edited, and Folder columns, beside a folder tree

Every shared document in the project, with its type, folder, author, and last edit.

In Shared Docs you get a document tree on the left, a tab strip across the top for the documents you have open, and a breadcrumb showing organization, project, folder, and document. The tree and the comments panel are both resizable by dragging their edges, or with the arrow keys once a handle is focused. Double-click a handle to reset it. If your organization has several projects, the project switcher sits at the top of the tree and shows how many shared documents each one holds. Your open tabs, panel widths, and last-used project are remembered in the browser, so returning to the console puts you back where you were. #### Editing together Shared markdown documents are live. Above the document, a status pill reports the connection (**Live**, **Connecting**, **Reconnecting**, **Offline**, or **Read-only**) and a save chip reports whether your changes are saved. The document stays hidden until the first sync completes, so you never type into what looks like an empty document while the server copy is still loading. Each teammate editing with you appears as a colored cursor labeled with their name. Screen readers announce people joining, leaving, and editing. Edits go both ways. Anyone whose organization role allows it can type into the document from the browser, and those changes reach the desktop app and every other open browser as they happen. Viewers and guests are held to reading. #### Commenting Select any text in the document and choose **Add comment**. Comments dock in a panel on the right, which you can toggle from the floating comments button. The button carries a count when the panel is closed. * Reply to a thread, then **Resolve** it once it is handled. * Type `@` in the composer to mention a teammate. * Mentioned teammates are notified.
A shared plan open in the browser with the comments panel docked on the right, showing four threads anchored to passages, each with an author, a timestamp, a reply box, and Resolve and Delete actions

Comments anchor to the passage they are about, with replies and resolve in the docked panel.

Commenting depends on your organization role. Owners, admins, and members can write comments. Viewers and guests can read but not comment. Comments are also withdrawn on any document the server has made read-only for you. #### Opening in the desktop app Every document has an **Open in desktop** link in its status bar that hands the document off to Nimbalyst on your machine. Documents the browser cannot handle offer the same handoff more prominently. ### Organization administration Switch the left navigation to **Organization** for five sections: | Section | What it covers | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Overview** | Your role, membership type, and every project in the organization | | **Billing** | Current plan, status, seat count, and period end; seat changes and payment management run through the billing provider, and the console never sees card details | | **Roles and members** | The member list, each person's role, role changes, member removal, and email invitations | | **Security** | Data custody mode, encryption key epoch and fingerprint, and the twenty most recent organization audit events | | **Danger zone** | Merge this organization into another, or delete it permanently | Deleting an organization requires typing its exact name. Role changes and every other privileged write are checked again by the collaboration service, so the console never grants access on its own. ### What the browser cannot do The console is deliberately narrower than the desktop app. Today: * **Only markdown documents open.** Mockups, diagrams, data models, mind maps, spreadsheets, and code files show as unsupported and need the desktop app. * **Trackers are desktop-only.** The shared tracker boards do not open in a browser. * **Documents above 8 MiB of collaborative state** are too large for a browser tab and offer a desktop handoff instead. * **No document history or version view.** * **No export or embedding.** * **No promoting a local file to the team.** Sharing a local file to your organization happens in the desktop app. * **No personal (non-team) documents**, and no read receipts. * **No creating projects or organizations.** The console works with organizations and projects that already exist. ### Troubleshooting | What you see | What it means | | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | **No access to this organization** | The link points at an organization your account cannot open. Check you signed in with the right address. | | **Organization access was removed** | Your membership ended while you had the document open. Live access stops immediately. | | **Document not found** | The document was deleted, or it left the project you have access to. | | **Your session expired** | Sign in again. Your destination is preserved. | | **Shared documents are unavailable** | The collaboration service could not be reached. Your route is kept, so a retry returns you to the same place. | | **This document is too large to edit in a browser** | Nothing is lost. Open it in the desktop app, which has no such limit. | | **This document is now read-only** | The server rejected an edit. The rejected change was not saved. | | **This document could not be opened** | The first sync did not complete. Nothing you type would be saved, so editing stays off until the connection returns. **Try again** retries it. | If a sign-in link fails, it has usually been used already or expired. Request a fresh one. ### Related * [Team Collaboration Overview](/team-collaboration/overview.md) * [Collaborative Documents](/team-collaboration/documents.md) * [Set Up Nimbalyst Teams and Organizations](/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/web-console.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.