Next.js Supabase V3 (#463)
Version 3 of the kit: - Radix UI replaced with Base UI (using the Shadcn UI patterns) - next-intl replaces react-i18next - enhanceAction deprecated; usage moved to next-safe-action - main layout now wrapped with [locale] path segment - Teams only mode - Layout updates - Zod v4 - Next.js 16.2 - Typescript 6 - All other dependencies updated - Removed deprecated Edge CSRF - Dynamic Github Action runner
This commit is contained in:
committed by
GitHub
parent
4912e402a3
commit
7ebff31475
18
docs/recipes/personal-accounts-only.mdoc
Normal file
18
docs/recipes/personal-accounts-only.mdoc
Normal file
@@ -0,0 +1,18 @@
|
||||
---
|
||||
status: "published"
|
||||
title: 'Disabling Team Accounts in Next.js Supabase'
|
||||
label: 'Disabling Team Accounts'
|
||||
order:
|
||||
description: 'Learn how to disable team accounts in the Next.js Supabase Turbo SaaS kit and only allow personal accounts'
|
||||
---
|
||||
|
||||
Disabling team accounts and only allowing personal accounts is a common requirement for B2C SaaS applications.
|
||||
|
||||
To do so, you can tweak the following environment variables:
|
||||
|
||||
```bash
|
||||
NEXT_PUBLIC_ENABLE_TEAM_ACCOUNTS=false
|
||||
NEXT_PUBLIC_ENABLE_TEAM_ACCOUNTS_BILLING=false
|
||||
```
|
||||
|
||||
That's it! Team account UI components will be hidden, and users will only be able to access their personal account.
|
||||
Reference in New Issue
Block a user