Projects

Organize and manage your prompts, experiments, and team collaboration

What is a Project?

A Project is the top-level organizational unit in LaikaTest. It serves as a container for:

Prompts: All your prompt templates and their versions
Experiments: A/B tests and experiment configurations
API Keys: Authentication credentials scoped to the project
Analytics: Usage metrics and performance data

Best Practice: Create separate projects for different applications, environments (dev/staging/prod), or teams. This keeps your prompts organized and makes collaboration easier.

Creating a Project

Projects are created and managed through the LaikaTest dashboard:

Log in to your LaikaTest dashboard
Click "Create Project" in the projects section
Enter a project name and optional description
Select an organization (if applicable)
Click "Create"

Dashboard Only: Project management (create, update, delete) is only available through the web dashboard. API tokens are scoped to individual projects and cannot manage projects themselves.

Project Structure

Each project contains:

Metadata

• Project name and description
• Creation date and last modified
• Organization association (if applicable)

API Keys

Each project has dedicated API keys for authentication. Keys are scoped to the project, ensuring secure access control.

Prompts

All prompts belong to a project. A prompt cannot exist without a parent project.

Experiments

Experiments are project-scoped and can only reference prompts within the same project.

Organizations & Projects

Projects can belong to an organization for team collaboration:

Personal Projects: Projects without an organization are private to your account
Organization Projects: Projects within an organization are accessible to all organization members based on their role
Access Control: Organization admins can manage project access, while members can view and use prompts

Managing Projects

All project management operations are performed through the dashboard:

View Projects: Access your projects list from the dashboard home
Update Projects: Edit project name and description in project settings
Generate API Keys: Create API tokens scoped to each project
Delete Projects: Remove projects and all associated data (irreversible)

Warning: Deleting a project will permanently delete all associated prompts, prompt versions, experiments, and analytics data. This action cannot be undone.

Best Practices

Use descriptive names: Name projects after the application or feature they serve (e.g., "Customer Support Bot", "Email Marketing")
Separate environments: Create different projects for development, staging, and production
Organize by team: If working with multiple teams, create projects per team or product area
Regular cleanup: Archive or delete unused projects to keep your workspace organized
Document purpose: Use the description field to explain the project's purpose and scope

API Token Workflow

Once you've created a project through the dashboard, follow this workflow for programmatic access:

1. Create Project: Use the dashboard to create a new project
2. Generate API Token: Navigate to project settings and create an API key
3. Create Prompts: Add prompt templates through the dashboard
4. Use SDK: Fetch prompts and run experiments using the API token in your application

Next Steps

Now that you understand projects, learn how to use them with the SDK:

Authentication - Generate and use API tokens for your project
Prompt Management - Create and version your prompt templates
Quick Start Guide - Get started with the SDK