mirror of
https://github.com/supabase/supabase.git
synced 2026-10-11 04:15:04 +03:00
Pamela Chia
e09a663292
## Summary Customers were upgrading to Pro to clear service restrictions, unaware that restrictions aren't lifted immediately when the billing cycle resets — there's a delay. This adds a clarifying note to both the docs FAQ and the Studio restricted alert so users know what to expect. Note: upgrading your plan or disabling spend cap *does* lift restrictions immediately (unchanged). The delay only applies to the billing-cycle-reset path for usage-limit violations. ## Changes - `billing-faq.mdx`: Removes the implication that restrictions clear the moment the billing period resets; adds "Note that there may be a short delay after your billing period resets before restrictions are fully lifted" - `Restriction.tsx`: Updates the restricted alert to make clear that upgrading lifts restrictions immediately, while the billing-reset path may have a delay ## Testing To test the Studio banner, find or create an org with `restriction_status === 'restricted'`, or temporarily hardcode `shownAlert = 'restricted'` in `Restriction.tsx` to preview: - [x] Restricted alert reads clearly and distinguishes immediate (upgrade) vs delayed (billing reset) paths - [x] Docs FAQ answer under "How can I remove restrictions" reads correctly with the new caveat ## Linear - fixes GROWTH-704