Choose Your Path

Choose Your Path

CCAM serves three overlapping roles. Pick the path closest to today's job; you can switch paths at any time.

Individual user

Goal: understand what your coding agents did, what remains, and what it cost.

Recommended sequence:

1. Start Here
2. Reading the Dashboard
3. Investigating Sessions and Agents
4. Kanban and Task Progress
5. Tokens, Costs, and Analytics
6. Personal Workspace Configuration

Your main safety habit is to treat status as evidence, not a verdict. Cross-check the most recent event and transcript before stopping a process or declaring it stuck.

Team administrator

Goal: make ingestion dependable, control access, preserve history, and make failures observable.

Recommended sequence:

1. Deployment Decision Guide
2. Security and Remote Access
3. Hook Health and Ingestion
4. Backups, Restore, and Retention
5. Monitoring with Prometheus and Grafana
6. Upgrades and Rollback
7. Incident Response Runbooks

Your main safety habit is to keep a rollback artifact and a tested database backup before upgrades or retention changes.

Power user or integrator

Goal: query CCAM from scripts or agents, automate reactions, and extend workflows without bypassing guardrails.

Recommended sequence:

1. CLI Automation Patterns
2. MCP Workflows
3. Alerts and Webhook Recipes
4. Dynamic Workflows
5. Skills and Plugin Marketplace
6. Safe Config Explorer Usage
7. Integration Patterns

Your main safety habit is least privilege: keep readers read-only, enable mutations only for the process that needs them, and require explicit confirmation for destructive operations.

If several roles apply

Use the administrator path for the shared service and the individual path for daily investigation. Add power-user capabilities only after service health, authentication, and backups are in place. This ordering prevents automation from amplifying a weak operational baseline.