AdministrationPlatform

Platform configuration

Every instance-level setting, tab by tab.

Instance administrators configure the installation under Admin → Configuration in the main sidebar. Changes apply to every workspace on the installation.

Settings can also be supplied by a configuration file at deployment time, which is how Helm-based installations keep them in version control. A setting that comes from the file is shown locked in the UI, with a note to change the file and redeploy instead.

  • Public URL — the address people and agents use to reach OvalBee. Email links, sign-in callbacks and the MCP address shown to agents are built from it. Set it first.
  • Public flows workspace — the only workspace whose flows can be published as read-only public examples. Empty means publishing is off.
  • Library catalog URL — where the template library, live examples and case studies come from. It points at the official OvalBee library by default.
  • Dataset retention — how long short-lived and long-lived working datasets are meant to be kept.
  • Request tracing — diagnostic tracing and the threshold for logging slow database queries.

All user accounts on the installation, with their sign-in provider, instance role and last sign-in. Create accounts, edit them, set passwords, and deactivate or reactivate users. See Sign-in and accounts.

  • OpenAI — the API key and model for AI Chat in the flow editor. Without a key, AI Chat is off. Agents connected over MCP use their own model and don’t need this.
  • Diagnostics — a Sentry DSN for error reporting.
  • Product analytics — PostHog settings.

SMTP host, port, security, credentials and the sender address. Leave the host empty to turn email off. Invitations and password resets need it.

Token lifetimes, secure cookies, the signup form, external sign-in providers (OpenID Connect, Google, GitHub) and bot protection. See Sign-in and accounts.

Whether node runs start as Docker containers or Kubernetes pods, and the backend’s options, including machine classes such as gpu. See Compute.

Where files are kept. Providers describe the storage backends — S3-compatible storage (AWS S3, MinIO, Ceph and similar), Azure Blob Storage, or a filesystem path — and Workspace storage picks the one workspaces use. Bucket routing optionally sends specific bucket names to a different provider, for data that lives outside the main storage.

On self-hosted installations, the installation’s plan and license. On OvalBee Cloud, billing is per workspace instead, under Settings → Billing.