Skip to main content
User settings control your own profile and personal access to Delphina. Open them from the account menu, or go to Settings. The tabs are General, Data Sources, Connect to Delphina MCP, and API Key. For organization-wide identities used by scripts and integrations, see Service Accounts instead.

​
General

  • Name — your display name across Delphina.
  • Bio — an optional short description of your role and focus.
  • Email — the address you sign in with. It’s read-only and managed through your organization’s authentication.
  • Browser notifications — toggle notifications when the agent finishes long-running work.
  • Theme — Light, Dark, or System.

​
Data Sources

Connect your personal credentials to the data sources your workspaces use, so the agent queries as you. Delphina lists each connection with its type (Snowflake, BigQuery, Databricks, or MCP) and status.
  • Connect — start the sign-in flow for a source that uses per-user OAuth.
  • Disconnect — sign out and remove your personal credential for that source.
Which sources appear here depends on how your workspaces’ warehouse connections and MCP connections are configured. Sources that use a shared service credential won’t ask you to connect.

​
Connect to Delphina MCP

Set up MCP-compatible clients (Claude Code, Claude Desktop/Cowork, Codex, Cursor, and others) to call Delphina from your development environment. See Delphina MCP Server for the full setup.

​
API Key

The API Key tab holds your personal credentials for the Delphina HTTP API. Both authenticate as you, scoped to your own roles and workspaces.
API access may need to be enabled for your account. If the tab shows that API key access isn’t available, contact your Delphina administrator.

​
API key

Your account’s long-lived API key. Unlike tokens, it’s re-copyable from this page at any time. Send it as a bearer credential:
Use the Authorization Header field to copy the full header value in one step.

​
API tokens

API tokens are individually revocable credentials with optional expiration — the preferred way to authenticate personal automation. You can hold several at once and revoke any one without affecting the others. Create a token
  1. Click + Create token.
  2. Optionally give it a Name to identify where it’s used.
  3. Choose an expiration: No expiration, or 7 / 30 / 90 / 180 / 365 days.
  4. Click Create token.
Delphina shows the full token once, with a ready-to-paste Authorization: Bearer … header. Copy it now — for security, it’s never shown again. Afterward the list shows only a masked form (prefix + last four characters), along with each token’s created date, last used date, and expiration. Revoke a token Click the trash icon on a token row and confirm. Revocation is immediate and cannot be undone; any integration using that token stops working. Revoked tokens are hidden by default — toggle Show revoked to see them. Send a token the same way as the API key:

​
Choosing between them

  • Prefer API tokens for new integrations: you can scope their lifetime with an expiration and revoke them individually.
  • The single API key is convenient for quick, personal use because it can be re-copied at any time.
  • For access owned by a team or system rather than a person, use a service account.
Keep all credentials secure — never commit them to source control, and revoke any that may have been exposed.