---
date: 2026-10-14
title: Share LLM connections across projects
description: Configure LLM credentials once at the organization level while allowing projects to override them when needed.
author: Tobias Wochinger
canonical: /docs/administration/llm-connection#organization-and-project-connections
ogImage: /images/changelog/2026-10-14-organization-llm-connections.png
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/docs/administration/llm-connection#organization-and-project-connections) and the API/SDK reference (https://api.reference.langfuse.com).

You can now configure LLM connections at the organization level and automatically share them with every project in the organization. This makes it easier to use centrally managed credentials for the Playground, evaluations, and experiments without repeating the same setup in each project.

- **Manage credentials centrally** in **Organization Settings > LLM Connections**.
- **Use different credentials in one project** by creating a project connection with the same name. The project connection takes precedence.

Organization owners and admins can manage shared connections in the UI. On Enterprise Cloud and self-hosted Enterprise Edition, they can also manage them through the public API with an [organization-scoped API key](/docs/administration/scim-and-org-api).

Learn more about [organization and project LLM connections](/docs/administration/llm-connection#organization-and-project-connections).

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-10-14-organization-llm-connections.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.