Suspending a project, not just an app

Admins can now suspend a whole project: every app stops, Kaisen is blocked, members keep read-only access and backups, and unsuspend restores only what that suspension stopped.

Share

We just shipped project suspension. Until now an admin could suspend a user (their personal apps stopped) or a single app. That left two gaps, and we hit both. Abuse in a shared team project could only be stopped app by app. And Kaisen ignored suspension: a build a suspended user had started kept running on the project's key and kept redeploying its preview. The rule now is simple: if abuse turns up, suspend the whole project.

What suspending a project does

  • Every app in it stops. On production that took about 13 seconds.
  • Kaisen (which is in preview) is blocked there: no new builds, runs or deploys, and running builds stop, including a turn already in flight.
  • Members keep read-only access and can still download backups. Any change returns a 403, and restoring into the project is refused.
  • Owners see a banner with the admin's reason. Other members see "Ask a project owner or the platform admin why".

It lives on the admin Projects tab. A reason is required; there's no type-the-name step because it's reversible. Suspending a user needs a reason too now. It suspends their personal project and stops every Kaisen run they started in any project, but leaves their team projects running for everyone else.

Seeing and undoing it

A new Suspensions tab lists every suspended user, project and app with the reason, when and by whom. Apps stopped because of their project or user sit under that cause, with an "Unsuspend the project" link instead of their own button.

Unsuspend restores only what that suspension stopped. Each app now records why it's suspended: by its user, its project, or an admin directly. An app an admin suspended on its own stays suspended when its project is lifted, and it can't be restarted on its own while its project or owner is still suspended.

How we checked it

Design and mockup first, then 62 unit tests plus a sweep confirming about 30 member write routes refuse a suspended project, as owner and as plain member. The security review (K45 to K51) made the write guard fail closed on unknown requests, closed paths where unsuspending could revive apps while the owner was still suspended, re-checks a restore queued before the suspension, rejects reasons with control or invisible characters, and discards a Kaisen turn already in flight. We ran the migration both directions on a throwaway MySQL before release, since MySQL can't roll back schema changes.

Then live end-to-end tests on production with throwaway apps. They found one more real gap: an app suspended on its own, then caught in a project suspension, could still be restarted by an admin inside it. Fixed, rerun, passing, and those scenarios are now part of the live suite (about 3 minutes).

A bug fixed along the way

Suspending a signup that hadn't been approved yet, then unsuspending it, made the account active and skipped approval. The platform now records the status a user had when suspended and returns them to it, so a pending signup goes back to pending. Users suspended before this change keep the old behaviour, since there's no record of whether they were approved.

This was the item we called next in the round 3 post.