> 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/setup-nimbalyst/settings-scopes.md). # Application, Account, and Project Settings Nimbalyst separates settings into three scopes so it is clear whether a change applies everywhere, to a signed-in identity, or only to the current project. Open Settings with **Cmd/Ctrl+,** or from the account menu, then choose **Application**, **Account**, or **Project** at the top. ## Application Application settings follow this Nimbalyst installation across projects. Use this scope for: * Notifications and themes * Voice Mode and agent features * Agent and chat providers * The extension Marketplace and installed extensions * Application-level MCP servers * Tools and token-cost controls * Advanced and database settings Choose Application when a provider, extension, MCP server, or preference should be available in every project you open. ## Account Account settings manage signed-in Nimbalyst identities and personal device sync: * Add, reconnect, switch, or sign out of accounts * Choose the account used for personal and mobile sync * Pair and manage devices * Choose projects and documents that sync to mobile * Manage shared links owned by an account You can sign in with multiple accounts. A project, organization, or shared link can belong to a different account from the one used for personal mobile sync. ## Project Project settings apply only to the current workspace: * Sharing and organization membership * Agent permissions * Tracker configuration * Project-specific AI provider overrides * Project-level MCP servers * GitHub integration * Project extension settings Project-level MCP servers and provider overrides are useful when a tool or model should be available only inside one repository. ## Organization Management Organizations have a dedicated management dialog rather than a fourth Settings scope. Open it from the organization switcher (**Manage organization…**), the account menu, or **Manage** on an organization row in **Settings > Account > Accounts**. Use it to manage: * Members, invitations, and roles * Projects in the organization and who can access each one * Organization messaging, security, and encryption * Billing, and organization deletion under Danger zone **Window > Organization Messages** is separate. It opens the messaging window for rooms and direct messages, not administration. See [Set Up Nimbalyst Teams and Organizations](/team-collaboration/setup-teams-and-orgs.md) for the full walkthrough. ## Extension Settings Extensions can add their own first-class pages under Application or Project settings. A Project extension page receives the current repository as context, so the same extension can keep different configuration in different projects. If an extension page is missing, confirm that the extension is installed and enabled in the same scope. ## Choosing the Right Scope | You want to change… | Use | | ------------------------------------------------------------------- | ------------------- | | Theme, notifications, default agent, or a tool used everywhere | Application | | Signed-in accounts, mobile sync, devices, or shared links | Account | | Permissions, Trackers, sharing, GitHub, or tools for one repository | Project | | Team roster, invitations, or organization projects | Organization dialog | --- # 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/setup-nimbalyst/settings-scopes.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.