---
date: 2024-08-13
title: Organizations
description: Introducing organizations to manage projects and permissions across larger teams working in Langfuse.
author: Marc
canonical: /docs/administration/rbac
---

> **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/rbac) and the API/SDK reference (https://api.reference.langfuse.com).

## What are Organizations?

Until now, access control in Langfuse was purely based on projects and roles. This led to a flat structure that was not suitable for larger teams working on multiple projects. `Organizations` are top-level entities that contain projects. They allow for a more structured approach to managing users, projects, and permissions.

```mermaid
graph LR
  A["User (via UI)"] -->|role| B[Organization]
  B -->|1:n| C[Projects]
  C -->|n:1| D[API Keys]
```

## Changes to the UI

Start page to view all organizations and projects

![Start page](/images/changelog/2024-08-13-organizations/organization-home.png)

Navigate between projects with new project selector

Settings are now organized by level (organization/project) and topic

## Migration

### Automated migration of existing projects

A new organization has been created for each existing project.

- The organization name is the same as the project name.
- All user permissions were migrated to the organization level. This ensures that all existing projects and users can continue to work as before.
- API Keys are unaffected by the migration and remain associated with the project.

### Group projects into a single organization

If you work with multiple projects in Langfuse, you can group them into a single organization by transferring projects via the project settings.

This transfer will centralize user management and permissions in an organization. The project remains fully operational as API keys, settings (except for access management), and data will remain unchanged and associated with the project. All features (e.g. tracing, prompt management) will continue to work without any interruption.

## Self-hosting configuration options

This change added new configuration options for teams that self-host Langfuse:

- Assign new users automatically to an organization via `LANGFUSE_DEFAULT_ORG_ID` and `LANGFUSE_DEFAULT_ORG_ROLE`.
- Enterprise Edition: Manage allowlist of users who are allowed to create new organizations via `LANGFUSE_ALLOWED_ORGANIZATION_CREATORS`.

## Learn more

- [RBAC Documentation](/docs/rbac)
- [API Reference](https://api.reference.langfuse.com)

<!-- 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/2024-08-13-organizations.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>.