VD Studio

Appearance

Org Settings ​

What's on this screen ​

Org Settings is where platform administrators manage settings that affect the whole Studio instance. The navigation includes Data Platforms, Capacity, Identity Providers, GitHub, Users, and other organization-wide panels.

How to open Org Settings ​

  1. Open Settings.
  2. Choose the organization settings area.
  3. Select one of the Org Settings panels from the left navigation.

How to choose a panel ​

  1. Select Data Platforms to configure Fabric, MotherDuck, or DuckDB Local platform entries.
  2. Select Identity Providers to add, edit, or remove sign-in and Domain-delegation providers.
  3. Select GitHub to configure the GitHub Commit Provider.
  4. Select Users to manage platform and Domain access. When Studio runs with ambient authentication (AUTH_ENABLED=false), the instance has a single operator; enable delegated authentication to add users. Existing users and their access remain manageable.
  5. Select Capacity to limit concurrent Ephemeral Workspaces and driving AgentSessions.

Capacity ​

Vibedata Owners can set four independent limits:

  • Concurrent Ephemeral Workspaces across Fabric and MotherDuck Domains. DuckDB Domains do not count.
  • Concurrent Intent AgentSessions.
  • Concurrent generic AgentSessions.
  • Concurrent AgentSessions attributed to one User across both profiles.

Leave a field on Unlimited when Studio should not apply that product limit. Saving a value below current usage does not stop existing work; it prevents new work until enough sessions or workspaces finish.

When interactive work reaches a limit, Studio names the exhausted resource and whether the instance or User limit caused it. Retry after work finishes or ask a Vibedata Owner to adjust the limit. Agent-backed Automation Runs wait in the queue instead of failing for capacity.

Remove a user ​

Use Remove to delete another user and all of their platform and Domain access. For a signed-in user, removal also ends active sessions and deletes personal credentials; it cannot be undone. Studio blocks removal of the last Vibedata Owner or the last User Access Administrator. Assign the protected role elsewhere before retrying. Removing a user who still owns a Domain or is referenced by an Intent is allowed — a Vibedata Owner or User Access Administrator can reassign those afterward.

Approve a user who signed in ​

A signed-in user awaiting approval appears as Pending approval. Select Approve to make the user valid without assigning roles. A role-less approved user appears as Valid — no access, and the action changes to Edit. Select Edit, choose the required access, and select Save when roles are needed.

An administrator-added user who has not signed in appears as Pending sign-in and is already approved. They need no role or Domain membership to complete first sign-in and use self-service; any assigned access becomes available after that same sign-in.

Add a user before they sign in ​

  1. Open Users and select Add user.
  2. Enter the user's verified sign-in email.
  3. Optionally choose platform or Domain access. Leave every access control empty to pre-approve a role-less user.
  4. Select Save. A valid email enables Save even without an access assignment.

The new entry is Pending sign-in and already approved. On the user's first successful sign-in, Studio reconciles the identity to that entry and makes the user valid. Add access later with Edit if needed.

Add a GitHub SSO user ​

When GitHub is the user's sign-in provider, enter the user's verified primary GitHub email in the Email field:

  1. Ask the user to open GitHub Settings → Emails and identify the address marked Primary and Verified.
  2. In Studio, open Users and select Add user.
  3. Enter that address in Email, optionally choose access, and select Save.

GitHub accounts can have more than one email address. Studio uses the verified primary address when GitHub provides one; it does not match every email on the account. Without one, Studio uses the first address GitHub returns; if GitHub does not return an email list, Studio may use the profile email. These fallbacks can be secondary or unverified addresses, so do not use them to pre-provision access. If a user signs in and sees Awaiting access, compare the email shown there with the pending entry; remove the incorrect pending entry, then grant the signed-in user the intended access.

What you'll see ​

  • Panel navigation — each Org Settings panel is shown as a left-navigation item.
  • Empty state — each panel explains when no rows are configured.
  • Loading — panels show loading text or skeleton rows while Studio fetches settings.
  • Error — panels show a repair message when Studio cannot load the relevant settings.

MCP Catalog ​

The MCP Catalog panel lists the supported MCP servers available to the organization. Studio refreshes the catalog automatically when you open the panel if you are allowed to manage it. While the refresh runs, the panel shows progress; if it cannot complete, it shows a retryable failure. Use Refresh catalog to retry manually.

Connector Sources ​

Vibedata Owners can use Connector Sources to register repositories that supply connector code:

  1. Select Add repository.
  2. Enter a stable lowercase name containing letters, numbers, and hyphens.
  3. Enter the repository in owner/repo, owner/repo#branch, or full HTTPS Git URL form (e.g., dlt-hub/verified-sources or https://github.com/acme/connectors). Specify the branch inline after # or in the separate Branch or tag field (defaults to main).
  4. Enter an optional description.
  5. Select Test. Studio enables Add repository after the URL and branch pass.
  6. Select Add repository.

Registration does not ask for credentials or clone the repository immediately. The daily Automation Job refreshes every registered source. Open Automations, select Connector source cache refresh, and inspect a run to see each repository's refreshed, unchanged, failed, or skipped outcome.

To remove a custom source, select Delete source-name, then Yes. Select Cancel to keep it. The official source has no delete action. A failed delete keeps the confirmation open and shows the error so you can retry. Deletion removes the registration and cached clone; later refresh runs no longer include that source.

LLM Profiles ​

Vibedata Owners can open Org Settings → LLM Profiles to configure the models available to Studio agents. In Profile name, enter 1–64 characters: start with a letter or number, and use only letters, numbers, periods, underscores, and hyphens. Names cannot end in .json. Invalid typed or pasted characters are rejected.

Studio supports up to 50 LLM Profiles. At that limit, existing profiles remain editable, but you must delete a profile before creating another.

Use the provider-model filter, or the Lab filter in Browse model catalog, to match any part of a visible label without changing the stored model. A no-match result is distinct from an empty, loading, or unavailable catalog. The manual model override remains a text field for provider-specific names.

How to set LLM execution behavior ​

  1. Open Org Settings → LLM Profiles.
  2. Create a profile or select Edit on an existing profile.
  3. Set Temperature, Max Output Tokens, and Reasoning Effort as needed.
  4. Select Create profile for a new profile or Save for an existing one.

Leave Temperature or Max Output Tokens empty to Use default. Select Use default for Reasoning Effort to let the model and provider choose their default behavior.

ControlAccepted value
TemperatureA number from 0 to 2, in steps of 0.1, or Use default.
Max Output TokensA whole number of 1 or more, or Use default.
Reasoning EffortUse default, Off, Low, Medium, High, or Extra high.

These values belong to the shared LLM Profile. Intents select a profile but do not have separate execution-setting controls. An AgentSession that is already running keeps the profile values it started with; Pause the Intent, then open it again, to apply a saved profile change to that session.