Organizations & Projects
ANTS Platform has two levels:
| Level | What it holds |
|---|---|
| Organization | Your company or business unit. Holds projects, members and roles, custom roles, billing, audit logs, data retention, feature visibility, notifications and organization API keys. |
| Project | A workspace inside an organization. Holds traces, sessions, prompts, datasets, scores, dashboards, project API keys, LLM connections, integrations, exports and the Discover AI and Budget AI settings for that project. |
Most companies need one organization. Data, API keys and most settings are scoped to a project, so a project is the main isolation boundary.
Use the switchers at the top of the page to move between organizations and projects. Organization Settings and Project Settings open from the header. The organization overview at /organization/<id> lists its projects.
Structuring projects
Common patterns:
- By application: one project per AI product or agent.
- By environment: separate projects for production and staging, or one project with the
environmentfield on traces. See Sending Data In. - By team: one project per team, with project roles to limit who sees it.
Create an organization
Start
Select New Organization in the organization switcher or on the organizations overview.
Follow setup
The setup flow asks you to name the organization, invite your team, create a first project and choose how to send data (Discover AI agents, the SDK, or both). You can skip the optional steps and finish them later from the settings pages.
Who can create organizations:
- Any user can create an organization with New Organization on the organizations overview. In the organization switcher, the option appears for people who are Owner of an organization.
- A Super Admin can turn on Only Super Admins create organizations under Platform → Settings. The new organization button is then hidden for everyone else and creation is refused for them. Its starting value is the deployment setting
ANTS_ONLY_SUPER_ADMINS_CREATE_ORGS(defaultfalse). - On a self-hosted Enterprise deployment, the operator can limit organization creation to a list of email addresses with
LANGFUSE_ALLOWED_ORGANIZATION_CREATORS. - A deployment can also add every new user to a default organization and project. See Members & Roles.
The person who creates an organization becomes its Owner. When a Super Admin creates one under Platform → Organizations → Create organization, they enter the first Owner's email instead: an existing account becomes Owner directly, anyone else gets an invite email, and the Super Admin is not added as a member. Organization names are 3 to 60 characters.
The organizations page
What the organizations overview shows depends on who you are:
| Viewer | What they see |
|---|---|
| Super Admin | Every organization, with Owners, members, projects, created date and status. Organizations they do not belong to are marked Not a member. A menu on each offers Manage Owners, Rename, Suspend or Reactivate, and Delete. |
| Member of two or more organizations | Their own organizations in the left panel. |
| Member of one organization (a demo organization does not count) | No left panel: the page opens straight on their organization, and the header shows its name. |
The organization switcher shows Super Admins every organization, with non-member ones marked Not a member.
Suspend removes an organization from its members' lists and stops them opening it, while its data, projects and ingestion are kept. A Super Admin can reactivate it at any time. Delete asks the Super Admin to type the organization name, and the organization's projects must be deleted first.
A self-hosted deployment can also give each organization a use case (Agents and governance, Budget AI, or Agents and Budget AI) that decides which modules and settings it shows. It is behind the instance switch ANTS_ORGANIZATION_USE_CASES (Helm web.config.features.organizationUseCases), off by default. While it is off, every organization shows both. When it is on, a Super Admin picks the use case in Create organization and changes it from Use case in the organization menu.
Create a project
Select New project in the project switcher. Project names must be unique in the organization. Creating projects needs the projects:create permission, which only the Owner holds among the built-in roles. Then create API keys for the project.
Organization General settings
Organization Settings → General shows:
- Name: rename the organization (Owner only).
- Logo: see Branding.
- Organization ID: for support requests and API calls.
- Projects, Members and Plan: a short overview of the organization.
- Delete this organization (Owner only). You can only delete an organization that has no projects, including projects still being deleted. Delete its projects first; project deletion can take a few minutes. Confirm by typing the organization name in lower case with spaces replaced by hyphens.
The Two-step sign-in switch, the prompt content switches and the read-only Data residency panel are on the separate Security tab. See Authentication & Security.
Project General settings
Project Settings → General shows:
- Name and Logo (Owner only).
- Project ID and Organization ID: for support requests and API calls.
- Host name: the base URL for SDKs and the API.
- Data retention: the organization's retention period, read-only. See Data Retention.
- Delete this project: type
<organization-name>/<project-name>(lower case, spaces replaced by hyphens) to confirm. Needsproject:delete(Owner among the built-in roles). The project's data and API keys are deleted in the background. Projects cannot be moved to another organization in the UI.
Deleting a project or an organization cannot be undone. Export anything you need first. See Data Exports.
Organization-wide feature visibility
Organization Settings → Features → Feature visibility turns these features on or off for every project:
| Switch | Default | Effect |
|---|---|---|
| AI Guardrails | Off | Shows or hides AI Guardrails. |
| AI Violations | Off | Shows or hides AI Violations. |
| Trace input and output | On | Shows or hides prompt and response content. Can be overridden per project. See Data Privacy. |
Viewing the tab needs tenantSecurity.features:read and changing it needs tenantSecurity.features:admin (Owner and Security & Compliance among the built-in roles).
Next steps
- Members & Roles: invite people and grant access.
- API Keys: connect apps to a project.
- Billing & Plans: what your plan includes.