Claim & share

Why claim

Anonymous deploy is live immediately. Claim within 60 minutes or drop again. Claim to keep the URL and unlock the project dashboard: private access, invites, secrets, domains, rollback, pause, destroy.

How to claim

1. After deploy, open the claimUrl printed by the CLI / MCP / Drop result (https://aft.page/claim?token=…), or use Claim on the live preview bar when you have the edit token.
2. Sign in with Google or a magic link.
3. The site appears under Projects. Same live URL.

The edit token is sensitive — treat it like a password until you claim. After claim, ownership is your account; the edit token alone can no longer manage the site.

Change URL

Random or long-title slugs happen. You can rename:

• Before claim: Preview → Change URL (needs deploy ?token=).
• After claim: Project → Overview / Danger → Change URL, or aft login && aft rename new-slug.

The old URL stops working immediately. Custom domains stay attached to the site. API: POST /v1/sites/{slug}/rename with { "slug": "new-name" }.

Private & invites

Owner: project Access (or preview Access) → Public / Private. Private sites require invite-by-email (view or edit). Edit can redeploy / rollback; view can open the live site only.

aft visibility private
aft visibility public

Invites and role changes are owner-only: POST /v1/sites/{slug}/invites with { "email": "…", "role": "edit" | "view" }. Revoke the same way you'd remove a collaborator from a shared doc — from the project's Access tab.

Redeploy & rollback

Redeploy in place keeps the same slug. History is on the project Deploys tab. CLI (after login):

aft rollback              # list
aft rollback dep_…       # restore prior deploy

Agents can use MCP aft_deploys / aft_rollback with the edit token before claim — mcp.md.

Pause & destroy

Two different levers, and it matters which one you reach for:

• Pause stops serving the live site (visitors see a "paused" page, HTTP 503) without deleting anything. Files, secrets, deploy history, and domains all stay put — flip it back on any time. PATCH /v1/sites/{slug} with { "active": false } (or true to resume).
• Destroy is owner-only and irreversible. It wipes the site row, every deploy, secrets, invites, members, and custom-domain attachments, then deletes the stored files. DELETE /v1/sites/{slug}. There's no undo and no recovery window — reach for pause first if you just want the site offline.

Ownership FAQ

Can a site have more than one owner? No — one account owns a claimed site. You can invite others as edit (redeploy, rollback, manage most of the project) or view (open the live site only), but there's no ownership-transfer flow today: the account that claims a site stays its owner until the site is destroyed.

What happens to collaborators, secrets, and domains if the owner destroys the site? All of it goes — see Pause & destroy above. If you want to keep the URL running under someone else's account, have them claim a fresh deploy rather than destroying an existing one.