Core Concepts
Understanding the data model helps you get the most out of Erold.
Tenant
A tenant is your workspace - the top-level container for all your data. When you sign up, you get one tenant. Think of it as your organization or team space.
- Each tenant has its own projects, members, and settings
- API keys are scoped to a tenant
- Data is isolated between tenants
Project
A project groups related tasks together. Each project has:
- Name - Human-readable name
- Key - Short identifier (e.g., "MYAPP") used in task IDs
- Description - Optional context
- Settings - Custom statuses, priorities, labels
Task
A task is a unit of work. Tasks have:
| Field | Description |
|---|---|
id | Unique identifier (e.g., "MYAPP-123") |
title | Task title |
description | Detailed description (Markdown supported) |
status | Current status (todo, in_progress, done, etc.) |
priority | Priority level (low, medium, high, urgent) |
assignee | Assigned team member |
labels | Tags for categorization |
dueDate | Optional deadline |
Knowledge Base
The Knowledge Base stores information that AI assistants can access. Use it for:
- Project context and goals
- Architectural decisions
- Coding conventions and standards
- API documentation summaries
- Team processes and workflows
Knowledge items have a key and content. AI can search and retrieve them automatically.
API Key
API keys authenticate requests to the REST API and MCP server. Each key has:
- Name - For identification (e.g., "Claude Code", "CI/CD")
- Permissions - Read, Write, or Admin access
- Scope - Can be limited to specific projects
Best Practice: Create separate API keys for each AI agent. This lets you track which agent did what and revoke access if needed.
Activity
Every action in Erold is logged as an activity. Activities track:
- What changed (task created, status updated, etc.)
- Who made the change (user or API key)
- When it happened
- The before/after values
This gives you a complete audit trail, including AI agent actions.