Set up AI (providers & keys)

Last updated About 3 hours ago

Set up AI (providers & keys)

Liza uses AI in three places: the AI assistant (chat/analysis in project context), the coding agents (desktop app), and scheduled AI tasks.

Two operating modes

Liza AI (included)Your own access (BYOK)
Setupnone – it is simply therestore the provider's API key
Billingthe workspace's AI creditdirectly with the provider
Available inpaid plansall plans (Free: one provider)
Providersoperated by Liza (Mistral platform, EU)Claude, ChatGPT, Gemini, Perplexity, Mistral …

In the AI chat you pick the provider via the pills above the input field. Only what is included in your plan, configured and allowed by your organization shows up.

Personal: your own keys

Settings → Personal → AI & connections

TabPurpose
My AI keysOne key per provider – applies everywhere (assistant + coding agent)
Coding agentConnect coding agents (desktop only) – see Agents
Liza accessAPI keys & MCP for programmatic access (developers)
UsageYour AI credit and consumption (only with included AI)
MemoryWhat the AI has remembered – see AI memory

Create keys with the respective provider:

ProviderCreate a key at
Claude (Anthropic)console.anthropic.com/settings/keys
ChatGPT (OpenAI)platform.openai.com/api-keys
Gemini (Google)aistudio.google.com/app/apikey
Perplexityperplexity.ai/settings/api
Mistralconsole.mistral.ai/api-keys
Black Forest Labs (images)dashboard.bfl.ai

Precedence: your personal key takes precedence over the org key. On the desktop it is additionally stored locally encrypted (keychain) so the coding agent can use it without a server – one field, both stores.

Organization: central keys & policies (admin)

Settings → Organization → AI – four tabs:

TabPurpose
Central keysStore providers' API keys centrally (encrypted). Assigned members then use AI without a key of their own.
AssignmentDecide per person which AI they may use – or release a key for everyone.
UsageOrg-wide consumption. Requires a separate admin/usage key from the provider (not the regular key).
PoliciesCentral lock: which AI providers are allowed in this organization at all.

Policies (central lock)

Blocked providers disappear from the AI chat selection for all members and cannot be used with a personal key either. There is also a switch "Forbid personal API keys" – then only central org keys and the included Liza AI remain.

Local desktop agents

A coding agent running on the machine with its own provider login (e.g. your own Claude or ChatGPT account) bypasses Liza. The lock hides it in the client but cannot technically enforce it.

AI credit (included Liza AI only)

The included AI is paid from a credit balance in euros. Purchased credit does not expire.

  • Personal credit – topped up per person.
  • Company credit – a shared pot. Per person you set a limit for how much they may spend from it per billing period (empty/0 = no access, or explicitly "no limit").
  • Topping up runs through Stripe's secure checkout; the credit is booked after successful payment.

This is managed under Settings → Organization → AI usage. In the AI chat an indicator shows the remaining credit; at 80% you get a warning, at 0 no new job starts.

Own keys ≠ credit

With your own key the Liza credit is irrelevant – you pay the provider directly. Credit notices only appear for the included AI.

Web vs. desktop

Web (browser)Desktop app
AI assistant (included or own access)
Personal/org AI keys✅ (+ local keychain)
Coding agents (files & commands)
Edit local files
Start/stop local dev servers

The coding agents run in the desktop app only, because they edit local files. Scheduled AI tasks, on the other hand, can run managed on the server – no desktop needed, see Schedule.