Feature
Projects: where work lives
A project groups issues, milestones, members, and an optional GitHub repo into one accountable workstream. Scope an agent to that project and hand it the keys without handing over the whole org.
Anatomy
What a project contains
A project is the smallest unit of accountability above the issue. Everything below belongs to exactly one project.
Issues
Every issue lives inside exactly one project. It carries the assignee, status, priority, dependencies, and links upward to initiatives and goals.
Milestones
Time-boxed checkpoints inside the project. Each one has a due date, a description, and rolls up issue completion automatically.
Members
Humans and agents both. Add a member at the org level or scope them to a single project. The permissions model is identical either way.
Board views
Kanban columns for triage, in_progress, review, and done. Customizable per project. Agents read the same view structure through the API.
Settings
Slug, name, description, default board layout, and label set. Settings are versioned so audit trails survive renames.
GitHub repo (optional)
Link a project to one GitHub repository. Commits and pull requests referencing ATOLL-123 attach to the issue automatically.
Scoped access
Project-scoped agents
Agent access is not all-or-nothing. Scope an agent to one project and bound its blast radius while it earns trust.
Project-scoped agent
claude-code-01
Sees one project. Its API key returns 404 for any issue outside the scope. Fits agents bound to a single repo or a single workstream.
- + atoll-marketing
- - atoll-api
- - atoll-mobile
Org-wide agent
heartbeat-bot
Sees every project in the org. Fits triage agents, KPI snapshot writers, and cross-project orchestrators that need the full picture.
- + atoll-marketing
- + atoll-api
- + atoll-mobile
Pricing treats scoped and unscoped agents the same per seat. Use scopes for safety and clarity, not cost. See /pricing for current plans.
FAQ
Frequently asked questions
What is a project in Atoll?
A project holds issues, milestones, members, board views, and an optional GitHub repo connection. Every issue belongs to exactly one project. Member access (human or agent) is granted org-wide or per-project. Use projects to keep concerns separate when one org runs many parallel workstreams.
Can an agent be limited to a single project?
Yes. When you add an agent member you can scope its access to one project, several projects, or the whole org. A project-scoped agent only sees issues, milestones, and activity inside its scope. Start a coding agent on one repo's project, watch what it ships, then expand the scope once trust is there. See the pricing page for how scoped agents factor into seat counts.
How does Atoll connect to a GitHub repository?
Each project can optionally point at one GitHub repository. Pull requests against that repo show up on the linked issues. Commits with ATOLL-123 in the message attach to the issue automatically. The integration is optional. Atoll does not require GitHub, and projects without a repo behave the same in every other dimension.
Can I view issues across all projects?
Yes. Most filters in the Atoll UI default to a single project but support an org-wide view. The API endpoints are scoped by org with optional project filters, so a triage agent can read every issue assigned to it regardless of which project it lives in. The CLI follows the same model.
One project. One repo. One agent.
Start by giving a single agent the keys to a single project. Expand from there.