A project is Repopack's shared boundary for a repository, tasks, collaborators, Jobs, Release products, and Apps. Project-local names and numbers only make sense within that project: task 42 or Job 1 in one project is unrelated to the same number in another.
Names, identities, and Git
The project name is an editable display label. Its permanent key is chosen when the project is created and remains reserved even after deletion. The key identifies /project/<key> URLs, the SSH/Git repository path, Release distribution URLs, and t-<key>-<task-number> preview hosts. Renaming the display name does not move the Git repository or change those addresses. The retained short ID serves internal uses; it is not a supported Release URL reference. Neither the name, key, nor short ID is an authorization credential.
rp bootstrap <project> clones and prepares a checkout; rp project link <project> connects an existing Git checkout. In a connected checkout, rp bootstrap reads project context and local instructions. Repopack advertises the canonical Git remote rather than asking clients to guess it from the website address. The Start page covers the first steps.
Access is explicit
Project permissions govern who can read code, take or review tasks, manage Jobs and Releases, and operate Apps. Owners have full project access. The configurable Guest role limits what signed-in non-members or members assigned Guest can do; it is not anonymous access. Other roles are project-defined. Being the task owner is also different from being an independent reviewer: review authority follows the account and project policy, not an agent's model name or session.
A browser action uses a signed-in session; rp and other programmatic clients use API authorization. Some sensitive API actions require a person to approve a guarded action in the browser before execution. The server rechecks the action and authorization at execution time. A browser session does not turn into an API token, and having a public Release channel does not make project code, Jobs, or the Releases management UI anonymously available. See Release distribution for that narrow public access boundary.
New projects require one approval before a task can be ready to merge, and eligible agent approvals submitted through the API count by default. This does not grant review permission or bypass reviewer independence, exact-head checks, or other merge gates. Project owners can change these settings under Settings → Controls. Existing projects keep their configured settings.
Project groups, where used, organize project lists; they do not grant permissions or change the project's Git or public identity. A project may be in at most one group.
For the built-in Owner and Guest roles and the rules for custom roles, see Project roles.