Project lifecycle and transfer
Rename, archive, restore, transfer, and permanently delete a project safely.
Project settings separate reversible identity and archive changes from owner-only transfer and permanent deletion.
Owners and admins can rename, archive, and restore. Transfer and permanent deletion require the organisation owner.
The display name and URL slug can change without changing internal project identity, flag keys, environment keys, or evaluation-key bindings.
The console URL changes when the slug changes. Update bookmarks, runbooks, and human-facing links. API automation should store durable IDs rather than parse console URLs.
Project slugs must use lowercase letters, numbers, and dashes. Reserved organisation navigation names are rejected.
Archive removes a project from ordinary active views and blocks normal management work while preserving configuration and activity.
Use archive when work is paused, an application is retired, or deletion needs a reversible checkpoint. Archived-project discovery remains available from the organisation project list.
Restore before editing resources or resuming ordinary work. Review old credentials, defaults, and application ownership after a long archive period.
Archive does not clear values already held in a running SDK. It also does not remove guarded code from application repositories.
The source actor must be owner and can transfer only to an organisation where they are owner or admin.
Before confirming:
Do not use transfer to bypass role, plan, billing, or organisation lifecycle restrictions.
If the destination uses the same slug, FeatureGate adds a numeric suffix. The internal project ID remains stable while the console URL changes.
Active runtime and client keys are rebound to the destination so evaluation can continue. Project-scoped management keys in the source are revoked because their authority cannot cross organisations.
Historical activity and API usage attribution remain with the source organisation. Source and destination both receive transfer events.
Runtime invalidation is published for active environments. Snapshot clients still need a successful refresh before they hold current state.
Only an owner can permanently delete a project, and the project must be archived first. Deletion is not the first step of application cleanup.
Before deletion:
Running SDKs may retain their last snapshot until refresh, restart, or discard. Deletion cannot erase customer-process memory.
401: replace a revoked source management key.Related pages: Projects, Activity and audit history, and Evaluation credentials.