# Application, Account, and Project Settings

Nimbalyst splits settings into application, account, and project scopes, so it is clear whether a change applies everywhere or to one project.

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.

Database Settings, under this scope, is where you look after a database problem. It can recover database copies Nimbalyst preserved rather than deleted, roll back a SQLite migration to the preserved PGLite copy, and explain why an automatic migration is being held back on this computer. Recovery and rollback keep the original data intact across restarts. See [Database Backups and Restore](https://nimbalyst.com/docs/troubleshooting/database-backups-and-restore/).

## 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](https://nimbalyst.com/docs/team-collaboration/setup-teams-and-orgs/) 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 |