Managing projects
Update settings, archive unused work, and restore access deliberately.
Project configuration#
Owners and admins can update a project's name, baseline branch, policy override, and capture settings. Keep the baseline branch aligned with the branch your CI uploads after merge. Capture-setting changes apply to new runs and may require fresh visual approvals.
Use Setup to maintain the repository workflow and token. A renamed project does not mean you should copy an upload token from another project.
Archive a project#
Archive an unused project from its settings. Read the confirmation:
- All project upload tokens are revoked, so CI uploads stop working.
- Queued or capturing runs are cancelled.
- Runs, snapshots, baselines, and review history remain readable.
- Reviews and other changes are disabled while it is archived.
- Usage recorded before cancellation still counts when applicable.
Archiving is reversible and deletes nothing. It is useful when you want to retain review history without allowing further uploads.
Restore a project#
An admin can restore the archived project. Create a new upload token and update your CI secret: restoring does not revive the old revoked tokens. Confirm the pipeline still builds the correct repository and branch before restarting it.
Trial restrictions#
Archiving or deleting a trial project does not reset the trial's one-project limit or create another trial. Check the plan before using lifecycle actions to reorganise a trial company.
Deletion#
Use permanent deletion only when you intend its stated effect and have the required permissions. For account or company data requests, follow the privacy notice or contact support. Do not assume archiving fulfils a deletion request.