From bfef22293bf89f513412210aa9852bf3fa91f7e1 Mon Sep 17 00:00:00 2001 From: Copple <10214025+kiwicopple@users.noreply.github.com> Date: Tue, 16 May 2023 17:31:47 -0700 Subject: [PATCH] Added a note for team members --- apps/docs/pages/guides/platform/going-into-prod.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/apps/docs/pages/guides/platform/going-into-prod.mdx b/apps/docs/pages/guides/platform/going-into-prod.mdx index 4e2c7c6fb84..bd6f42ad7bc 100644 --- a/apps/docs/pages/guides/platform/going-into-prod.mdx +++ b/apps/docs/pages/guides/platform/going-into-prod.mdx @@ -85,6 +85,15 @@ After developing your project and deciding it's Production Ready, you should run - When working with enterprise systems, email scanners may scan and make a `GET` request to the reset password link or sign up link in your email. Since links in Supabase Auth are single use, a user who opens an email post-scan to click on a link will receive an error. To get around this problem, consider altering the email template to replace the original magic link with a link to a domain you control. The domain can present the user with a "Sign-in" button which redirect the user to the original magic link URL when clicked. +### Access levels for Team Members + +As your team grows, you might want to consider the different levels of access that your team is given. + +- Free and Pro: Supabase provides access controls within the Dashboard for Developers and Administrators. +- Teams and Enterprise: these tiers include more advance access controls, including Read-only Roles for the Dahsboard. + +You might also consider running your workload across several organizations. It is a common pattern to have a Production organization which is restricted only to those team members who are qualified to have direct access to production databases. + ## Next steps This checklist is always growing so be sure to check back frequently, and also feel free to suggest additions and amendments by making a PR on [GitHub](https://github.com/supabase/supabase).