Administration

Who is the administrator

The administrator pages require the platform administrator role. Being the owner or an admin of an organization is not enough: every user owns their personal organization, and that does not reveal these pages. For a regular user the pages are simply absent from the settings list, and opening one by its address does not give access to it.

Becoming the administrator on a self-hosted install

On a fresh Community Edition install, the first person to register becomes the platform administrator, and lands on the first-run setup wizard (Connect to LiveContext Cloud, API Providers, CLI Providers, Platform Integrations, then You're all set!, or No provider configured when nothing was set up). Completing the wizard marks the install as set up: from then on no later account is promoted automatically, even if every user is removed. See Self-hosting for the wizard and for how teammates join afterwards.

Administrator pages on a self-hosted install

These pages appear in the settings list of a self-hosted administrator, in addition to the pages every user has (see Account & settings).

AI Providers

The page the agents and chat depend on. Its tabs are API Keys (a key per provider), CLI (the CLI bridges, one entry each in its own toggle: Claude Code, Codex, Gemini CLI, Mistral Vibe and Cursor), and Models (which models are enabled). The setup wizard fills the same settings. See Models & providers for each tab in detail.

Platform Keys

The page is titled Platform Credentials. Platform credentials (Client ID, Client Secret, API keys) are what let your users connect their own accounts through OAuth2, configured here instead of environment variables. Each integration card shows Configured or Not configured, and offers:

• A switch that turns the integration on or off for the install, and an expandable list of its endpoints (Endpoints, with how many are active).
• Configure (or Edit) to enter the secret fields. When an integration has several authentication methods, each gets its own tab and can be disabled separately. Leave a secret field empty to keep its current value.
• Pricing, once a credential is saved: publish a Markup Pricing version, a default markup in credits per call plus per-tool overrides. Each publish creates a new version; runs already in flight keep the version they started with.

The page opens on Configured, what is already set up; switch to All Integrations to find what is left to set up. Users then connect their own accounts from Credentials & Variables (see Integrations).

Node Types

Enable or disable workflow node types, filtered by category (Triggers, Actions, Control Flow, AI, Data and more). The page also has Integrations and Capabilities tabs, and a Minimum plan per node, integration endpoint or capability (for example vector search or email alerts).

The node catalog itself is described in Node reference.

Cloud

The Connection tab (Cloud Connection) links this install to a LiveContext cloud account with Connect to Cloud, or unlinks it with Disconnect. The link is what gives your users the cloud marketplace, referral rewards and automatic catalog updates. Once linked, two switches decide what runs through the cloud: LLM source (API model calls on the cloud account, billed in credits) and Integration credentials (integrations on LiveContext's credentials). Both need a paid plan on the cloud account. The Bundles tab shows the sync status of the signed Model catalog, Integrations catalog and Skills bundles, with Sync now. Linking and bundles are detailed in Self-hosting.

Version and updates

On a self-hosted install, Settings > Information starts with a Version card: the Edition, Version, Commit and Built on date of the running build. Every user of the install can see it.

The install checks the public release feed once a day and on startup. When a newer release exists, the card shows Update available (or Security update in red when the release contains a security fix), with How to update and Release notes. A dot also appears on Information in the settings list (red for a security update, amber otherwise). Otherwise the card reads You're on the latest version.

LiveContext never updates itself. How to update gives the commands to run from your cloned LiveContext folder. Pull the repository first: the Compose file pins the release image tag, so without it you would pull the old image again.

git pull
docker compose pull
docker compose up -d

Your data is kept, and database migrations run automatically on startup.

Below the version, Optional components shows whether the heavy features that are off by default are enabled: Interface screenshots & PDFs and Browser agent & web search.

Cloud operator pages

The settings code contains more administrator pages that serve the operator of the LiveContext cloud. They never appear on a Community Edition install:

On the cloud, Cloud lists the self-hosted instances connected to the account instead of a connect button.

Troubleshooting

Related pages