What they are
- Organisation: your company/team space. Members, roles, datasources, entities, and other shared configurations live here.
- Project: the workspace where traces, conversations, prompts, experiments, datasets, and scores are grouped and viewed.
Why it matters
- Clean separation between products or environments (prod vs staging).
- Permissions, searches, and configurations are scoped—reducing mistakes and accidental cross-environment visibility.
How it shows up in Arcane
- The header/sidebar lets you pick the active organisation and project.
- All feature pages (Traces, Conversations, Datasets, Scores, Experiments, Prompts) respect the current project.
- Configuration pages read/write within the active organisation.
Typical setups
- One organisation per company; projects split by environment (Prod, Staging) or by product line.
- Keep project names aligned with the services emitting traces to make filters intuitive.
- If teams are isolated, use separate projects and roles to keep data visibility tight.
Good practices
- Decide a naming convention early (e.g.,
product-env like chat-prod, chat-stg).
- Grant least-privilege roles per project; avoid blanket org-wide edit rights.
- Before importing entities or configs, double-check you’re in the right project to avoid cross-environment confusion.