mirror of
https://github.com/supabase/supabase.git
synced 2026-10-10 03:45:06 +03:00
Joshen Lim
1de298ff31
## Context Previous PR was [here](https://github.com/supabase/supabase/pull/45143) but it got stale with lots of conflicts so figured it'll be easier redo it off the latest master Moves policies page from Auth to Database under an Access Control section along with Roles. This moves all existing files, applies redirects, and updates urls to point to the new route <img width="274" height="412" alt="image" src="https://github.com/user-attachments/assets/7952c185-64ae-4355-ba36-45397efe1787" /> <img width="453" height="471" alt="image" src="https://github.com/user-attachments/assets/04b3dcb3-48a5-4049-9893-d01109fb46a9" /> ## To test - [ ] Verify that policies now live under Database correctly <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a quick navigation shortcut to open **Database > Policies (RLS)**. * **Bug Fixes** * Updated Policies and RLS-related links across the product to open the **Database policies** area (menus, command palette, context actions, alerts, and link-outs). * Added a permanent redirect from the old **auth policies** URL to the new **database policies** URL. * **Documentation** * Updated RLS Dashboard and security checklist instructions to reference **Database > Policies**. * **Tests** * Adjusted automated tests to validate the new Policies route. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
35 lines
3.2 KiB
Plaintext
35 lines
3.2 KiB
Plaintext
---
|
|
id: 'auth-general-configuration'
|
|
title: 'General configuration'
|
|
subtitle: 'General configuration options for Supabase Auth'
|
|
---
|
|
|
|
This section covers the [general configuration options](/dashboard/project/_/auth) for Supabase Auth. If you are looking for another type of configuration, you may be interested in one of the following sections:
|
|
|
|
- [Policies](/dashboard/project/_/database/policies) to manage Row Level Security policies for your tables.
|
|
- [Sign In / Providers](/dashboard/project/_/auth/providers) to configure authentication providers and login methods for your users.
|
|
- [Third Party Auth](/dashboard/project/_/auth/third-party) to use third-party authentication (TPA) systems based on JWTs to access your project.
|
|
- [Sessions](/dashboard/project/_/auth/sessions) to configure settings for user sessions and refresh tokens.
|
|
- [Rate limits](/dashboard/project/_/auth/rate-limits) to safeguard against bursts of incoming traffic to prevent abuse and maximize stability.
|
|
- [Email Templates](/dashboard/project/_/auth/templates) to configure what emails your users receive.
|
|
- [Custom SMTP](/dashboard/project/_/auth/smtp) to configure how emails are sent.
|
|
- [Multi-Factor](/dashboard/project/_/auth/mfa) to require users to provide additional verification factors to authenticate.
|
|
- [URL Configuration](/dashboard/project/_/auth/url-configuration) to configure site URL and redirect URLs for authentication. Read more [in the redirect URLs documentation](/docs/guides/auth/redirect-urls).
|
|
- [Attack Protection](/dashboard/project/_/auth/protection) to configure security settings to protect your project from attacks.
|
|
- [Auth Hooks (BETA)](/dashboard/project/_/auth/auth-hooks) to use Postgres functions or HTTP endpoints to customize the behavior of Supabase Auth to meet your needs.
|
|
- [Audit Logs (BETA)](/dashboard/project/_/auth/audit-logs) to track and monitor auth events in your project.
|
|
- [Performance](/dashboard/project/_/auth/performance) to configure and optimize authentication server settings.
|
|
|
|
Supabase Auth provides these [general configuration options](/dashboard/project/_/auth/providers) to control user access to your application:
|
|
|
|
- **Allow new users to sign up**: Users will be able to sign up. If this config is disabled, only existing users can sign in.
|
|
|
|
- **Confirm Email**: Users will need to confirm their email address before signing in for the first time.
|
|
- Having **Confirm Email** disabled assumes that the user's email does not need to be verified in order to login and implicitly confirms the user's email in the database.
|
|
- This option can be found in the email provider under the provider-specific configuration.
|
|
{/* - If you previously relied on this config to autoconfirm a user's email address, you can switch to use **Allow unverified email sign in** instead. This new option allows the user to sign in with an unverified email which you can keep track of through the user object. It provides more versatility if you require your users to verify their email address in the future since you can structure your RLS policies to check the user's `email_verified` field. */}
|
|
|
|
- **Allow anonymous sign-ins**: Allow anonymous users to be created.
|
|
|
|
- **Allow manual linking**: Allow users to link their accounts manually.
|