Projects

A project is the place for a related body of work in Continual. It connects source code, branches, apps, threads, automations, tasks, and the connections used by that work. Projects belong to a workspace.

Choose a useful boundary

Keep work in the same project when it should share source, connections, and app data. Use separate projects when work needs a different access boundary or independent configuration.

For example, a customer operations project can contain an internal dashboard, support automations, and the threads used to build and maintain them.

Work in a project

Start a thread to work with the agent. Build an app for a dedicated interface to the work. Add connections for external services, use automations for repeated work, and resolve requests in Tasks.

Project settings control shared configuration such as the model, source repository, environment variables, and tool permissions. Projects can use a managed repository or a connected repository.

Branches and data

Threads, apps, and automations run in a branch context. Database-backed apps on the same branch share its database. Check the branch when testing a change or investigating why two runs see different data.

App deployments are associated with individual apps on a branch. The Branches and environments page describes the future project-wide release and environment model.

Project access

Memberships and roles determine who can access and administer platform resources. Access to an external service also depends on its connection and provider permissions. See Workspaces and members for the workspace boundary.