Settings Overview
Settings is where you configure data sources, organization settings, and personal account preferences. Domain configuration has its own Domains destination in the global application rail.
Opening Settings
| Method | Action |
|---|---|
| Keyboard shortcut | Press Cmd+, (Mac) / Ctrl+, (Windows) |
| Gear icon | Click the gear icon in the navigation rail — Organization Settings |
| Account menu | Click your picture in the top-right corner — User Settings |
| Deep link | Navigate to ?tab=<section> query parameter |
The gear goes straight to Organization Settings. Your own settings — profile, theme, connections, API keys, sessions — open from the account menu.
If Studio is running without single sign-on (a local or evaluation install), the sections that only exist to configure sign-in and other people — Users, SSO Providers, Identity Providers, and GitHub — are not shown. That deployment has one operator, signed in from the host session, so there is nobody to invite and no provider to register. The welcome checklist says the same, in place of those steps.
Settings Layout
Settings is a two-column layout:
- Left column — The settings navigation with section labels and items.
- Right column — The content panel for the selected section.
Use Hide Organization settings navigation or Hide User settings navigation to give the selected page more room. Use the corresponding Show control to restore the section list. These buttons work with Enter or Space. Hiding navigation keeps your current page and unsaved input; hidden navigation items are skipped when you press Tab. The navigation list and page content scroll independently.
Recovering a settings change
Settings editors protect the configuration you reviewed, including budgets, capacity, providers, LLM profiles, announcements, user access, action confirmation, connections, MCP deployments, plugins, marketplaces, and custom automations. If that configuration changes while you are editing or confirming removal, Studio keeps your draft or confirmation open. Use the displayed reload action, such as Discard draft and reload, Reload and review, or Reload connections. A successful reload discards the old draft or selection so you can review the saved settings and submit again. If reload fails, your draft or selection stays open. Background updates do not silently replace your draft, and Studio does not automatically resubmit it.
When creating an LLM profile, announcement, provider, stored connection, connector source, marketplace, or custom automation, retrying unchanged input within 24 hours recovers the original completed result. To start a new attempt after resolving an external problem, cancel and reopen the creation form. An older browser tab that asks for a reload must be refreshed before submitting protected changes.
Navigation Structure
The left navigation is divided into two groups:
PROJECT
| Item | Purpose |
|---|---|
| Sources | Connect and manage data sources; configure Git and Fabric defaults |
| Skills | Manage AI knowledge modules that extend the agent's capabilities |
| Plugins | Manage plugin marketplaces, installation, and enablement |
ORG SETTINGS
| Item | Purpose |
|---|---|
| Org Settings | Open organization-wide settings such as Data Platforms, Identity Providers, and GitHub |
ACCOUNT
| Item | Purpose |
|---|---|
| Profile | Change your appearance theme and manage signed-in sessions |
| Action Confirmation | Control when agents pause for approval before running proposed actions |
| Connections | Manage GitHub and personal credentials required by Domain Data Platform and Secret Store requirements |
| MCP Servers | Connect and manage the MCP servers available to your account |
Managing Organization MCP Deployments
Vibedata Owners manage organization-wide MCP servers from Org Settings → MCP Catalog. Each catalog entry contains its deployments, so two deployments of the same server appear as separate named rows.
Add a deployment
- Find the catalog entry and select Add deployment.
- Optionally enter Name (optional). A useful name distinguishes deployments of the same server, such as separate workspaces.
- Complete every required field. The Endpoint, Environment, and Header labels show how Studio uses each value.
- Select Add deployment.
The dialog states that organization values are sent directly to Obot and are never shown again. Sensitive fields use password inputs. Studio shows the new row only after the deployment is configured and available to the organization.
Every supported catalog entry allows an initial deployment. Add deployment remains available after that only for entries that support multiple deployments.
Edit a deployment
- Select Edit on the deployment row.
- Change Name (optional). To clear the custom name, leave it blank.
- Enter organization values only when you need to replace them.
- Select Save changes.
Changing a name does not merge the deployment with another row. Users continue to connect to each deployment separately.
Remove a deployment
- Select Remove on the deployment row.
- Review the deployment name, deployment ID, and connected-user count when it is available.
- Select Remove deployment.
Only the selected deployment is removed. Its connected users lose access, while sibling deployments from the same catalog entry remain available.
Deployment states
- No deployments configured. — The catalog entry has no organization deployment.
- Ready — The deployment is available to eligible users.
- Not ready — Obot has not reported the deployment as ready.
- Cleanup required — Setup did not complete cleanly. The row can be removed but not edited.
- No supported MCP catalog entries — The catalog contains no entry Studio can configure.
- MCP catalog unavailable — Obot is not responding. Select Retry after it recovers.
Connecting an MCP Server
Open User Settings → MCP Servers. Each organization deployment appears as a separate row using its deployment name. Select Connect on the deployment you want to use.
- If the server needs no additional setup, Studio opens its authorization page.
- If the server needs a header or other value, complete the setup form and select Save. Studio then opens the authorization page.
- If the server authorizes you with your own token, the setup form asks for it. Studio saves it for your account only and opens no authorization page.
- If the authorization page does not open, select Connect OAuth on the server row to resume.
Deployments are organization-wide, not per Domain. A server you connect is available in every Intent you open, whichever Domain that Intent belongs to.
Return to Studio after authorization. Studio refreshes the row when the Settings window regains focus. Use Disconnect to remove your server connection, including its saved setup and authorization, or Retry when Studio cannot read its status.
Applying action-confirmation changes
Action-confirmation changes apply when the next agent session starts. To apply your saved settings immediately to an active Intent you are driving, return to the workspace, Pause the Intent, then open it again.
Navigating Between Sections
Click any item in the left navigation to switch sections. The active section is highlighted with a blue background.
Action Confirmation Changes
User Settings → Action Confirmation controls when the agent pauses before proposed actions.
Your own actions
Use my own confirmation settings — off by default, so the instance system default applies. Turn it on to choose your own risk level and unclassified-action behavior:
| Risk level | Behavior |
|---|---|
| Low | Pause on every classified action |
| Medium | Pause on Medium and High risk (system default) |
| High | Pause only on High risk |
Run unclassified actions without pausing — when on, actions the agent can't classify run without asking for approval.
Saved risk-level and unclassified-action changes apply when your next agent session starts. Agent sessions that are already active keep the confirmation settings they started with — Pause the Intent, then open it again, to apply them immediately.
Subagent actions
Below your own settings, Subagent actions governs the Subagents you delegate work to — not the risk level above, which applies to what the agent proposes to you directly.
Only confirm pre-approved actions — off by default, so a Subagent's actions are always approved automatically and only a protected runtime path is ever rejected. Turn it on and an above-threshold Subagent action must already have an always-allow grant (Tool, Command family, or Exact command); anything else is rejected automatically, without asking you.
Saving
Both groups share one Save button. It stays greyed out until you change something, and switching a toggle changes nothing on its own until you select Save — leave the screen first and your edits are discarded. Save submits only what you changed and tells you once whether it worked. Like the risk settings, a Subagent-mode change applies when your next agent session starts.
Always-allowed actions
Below the Save button, Always-allowed actions lists every action you've always-allowed from an approval request, grouped by kind — Exact command, Command family, or Tool — each with the date it was created. Click the trash icon next to an entry to revoke it. The footer shows "Showing X–Y of Z" with your true total; once you have more than 50 grants, use the Previous page / Next page buttons to move through the list, so nothing is hidden. If your registry grows past the 10,000 grants a single agent session can load, a red warning appears here telling you new agent sessions will fail to start until you revoke some (VD-5254).
Unlike the settings above, always-allow grants apply immediately: creating or revoking a grant takes effect on the very next matching action in any active agent session, with no need to pause and reopen the Intent. Grants apply at any risk level until you remove them.
Returning to the Workspace
Click the back arrow (←) at the top of the left navigation column (above the "Settings" heading) to return to the main workspace (activeView → workspace). You can also press Cmd+, / Ctrl+, again to toggle back.
Quick Reference
| Action | How |
|---|---|
| Open settings | Cmd+, or gear icon |
| Navigate to Domains | Left nav → Domains |
| Navigate to Sources | Left nav → Sources |
| Navigate to Org Settings | Left nav → Org Settings |
| Navigate to Skills | Left nav → Skills |
| Navigate to Plugins | Left nav → Plugins |
| Navigate to Profile | Left nav → Profile |
| Manage Domain connections | Left nav → Connections |
| Connect an MCP server | Left nav → MCP Servers → Connect |
| Open Action Confirmation | Left nav → Action Confirmation |
| Revoke an always-allow grant | Action Confirmation → Always-allowed actions → trash icon |
| Return to workspace | Click ← arrow at top of left nav |