Merge pull request #1156 from neondatabase/dprice-email-signup-changes

Updates for email login

content/docs/get-started-with-neon/signing-up.md

@@ -5,12 +5,12 @@ redirectFrom:
   - /docs/quickstart/console/
   - /docs/cloud/getting-started/
   - /docs/cloud/getting_started/
-updatedOn: '2023-10-24T18:56:54.981Z'
+updatedOn: '2023-11-02T17:14:39.696Z'
 ---
 
 You can sign up for free and upgrade to a paid plan when you are ready to scale. For information about our Neon Free Tier limits, see [Neon Free Tier](/docs/introduction/free-tier). For information about Neon's paid plan options, see [Neon plans](/docs/introduction/plans).
 
-Signing up for Neon is easy. Simply navigate to [https://console.neon.tech](https://console.neon.tech) and sign in with a Github or Google account.
+Signing up for Neon is easy. Simply navigate to [https://console.neon.tech](https://console.neon.tech) and sign in with your email, Github, or Google account.
 ![Neon console sign up](/docs/get-started-with-neon/neon_signin.png)
 
 After signing in, you are directed to the Neon Console where you can create your first project. For instructions, see [Create your first project](/docs/get-started-with-neon/setting-up-a-project).

content/docs/guides/project-sharing-guide.md

@@ -2,7 +2,7 @@
 title: Project sharing
 subtitle: Learn how to share your Neon project with others
 enableTableOfContents: true
-updatedOn: '2023-10-24T18:56:54.984Z'
+updatedOn: '2023-11-02T17:14:39.700Z'
 ---
 
 The [Neon Pro Plan](/docs/introduction/pro-plan) lets you share your Neon project with other users, giving them access to your Neon project from all supported Neon interfaces, including the Neon Console, Neon API, and Neon CLI. Follow this guide to learn how.
@@ -12,7 +12,7 @@ The [Neon Pro Plan](/docs/introduction/pro-plan) lets you share your Neon projec
 You can share your Neon project with anyone. The only requirement is that the user has a Neon account. The account can be a Neon Free Tier account or Neon Pro Plan account.
 
 1. If the user does not have a Neon account, ask them to sign up. You can provide your users with the following instructions: [Sign up](/docs/get-started-with-neon/signing-up).
-2. Request the email address associated with the account the user signed up with. For example, if the user signed up with their Google account, ask for the email address associated with their Google account.
+2. Request the email address the user signed up with. If the user signed up with a Google or GitHub account, ask for the email address associated with that account.
 
 ## Share your project
 

content/docs/introduction/auto-suspend.md

@@ -2,7 +2,7 @@
 title: Auto-suspend
 subtitle: Scale computes to zero when not in use
 enableTableOfContents: true
-updatedOn: '2023-10-24T18:56:54.987Z'
+updatedOn: '2023-11-03T11:49:30.938Z'
 ---
 
 Neon's _Auto-suspend_ feature controls when a Neon compute instance transitions to an `Idle` state (scales to zero) due to inactivity.

content/docs/introduction/autoscaling.md

@@ -2,7 +2,7 @@
 title: Autoscaling
 subtitle: Learn how Neon automatically scales compute resources on demand
 enableTableOfContents: true
-updatedOn: '2023-10-24T18:56:54.987Z'
+updatedOn: '2023-11-03T11:49:30.941Z'
 ---
 
 Neon's _Autoscaling_ feature, available for [Neon Pro Plan](/docs/introduction/pro-plan) users, dynamically adjusts the amount of compute resources allocated to a Neon compute endpoint in response to the current load, eliminating the need for manual intervention.

content/docs/introduction/compute-lifecycle.md

@@ -3,7 +3,7 @@ title: Compute lifecycle
 enableTableOfContents: true
 redirectFrom:
   - /docs/conceptual-guides/compute-lifecycle
-updatedOn: '2023-10-24T18:56:54.988Z'
+updatedOn: '2023-11-03T11:49:30.942Z'
 ---
 
 A compute node in Neon is a stateless Postgres process due to the separation of storage and compute. It has two main states: `Active` and `Idle`.

content/docs/introduction/pro-plan.md

@@ -3,7 +3,7 @@ title: Neon Pro Plan
 subtitle: Learn about the advantages of upgrading to the Neon Pro Plan
 enableTableOfContents: true
 isDraft: false
-updatedOn: '2023-10-24T18:56:54.990Z'
+updatedOn: '2023-11-03T15:31:59.569Z'
 ---
 
 The Neon Pro Plan plan is intended for users who have completed their evaluation of Neon on the Neon Free Tier and are ready to transition to a production-level plan with higher limits and advanced features.
@@ -32,7 +32,7 @@ The Neon Pro Plan comes with the following advanced features, and we plan to add
 - **Autoscaling:** The _Autoscaling_ feature automatically adjusts compute size based on demand. You set a maximum and minimum compute size, and the Autoscaling feature automatically scales compute resources between those boundaries for optimum performance and cost-efficiency. No manual intervention is required to handle sudden usage spikes, and no downtime is required to reconfigure system resources. Neon Pro Plan users can enable and configure Autoscaling in the Neon Console. For instructions, see [Autoscaling configuration](/docs/manage/endpoints#compute-size-and-autoscaling-configuration).
 - **Larger computes:** The Neon Pro Plan supports computes with up to **7 vCPUs and 28 GB of RAM**, providing the processing power  to handle any workload. By comparison, the Neon Free Tier provides .25 vCPUs and 1GB of RAM, which is great for prototyping and evaluation but less than needed at scale. For configuration instructions, see [Compute size configuration](/docs/manage/endpoints#compute-size-and-autoscaling-configuration).
 - **Configurable Auto-suspend:** The Neon Free Tier automatically suspends computes after 5 minutes of inactivity. With the Neon Neon Pro Plan, you can increase or decrease this time period, or you can disable the Auto-suspend feature entirely. A shorter delay, such as 60 seconds, can potentially reduce compute costs. A longer delay keeps your compute active for longer intervals, reducing the number of cold starts. To prevent cold starts entirely, in cases where even a few seconds delay is too much, you can disable the Auto-suspend feature entirely so that your compute is always active. The Auto-suspend feature is configured in the Neon Console. For instructions, see [Auto-suspend configuration](/docs/manage/endpoints#auto-suspend-configuration).
-- **Project sharing:** The _Project sharing_ feature allows you to share your Neon projects with other Neon users. Project sharing is managed on the **Settings** page in the Neon Console. Simply add the Google or GitHub email account of the user you want to share your project with. Projects can be shared with any Neon user, including Neon Free Tier users. Usage is applied to the project owner's Neon account. For instructions, see [Share a project](/docs/manage/projects#share-a-project).
+- **Project sharing:** The _Project sharing_ feature lets you share your Neon projects with other Neon users. Project sharing is managed on the **Settings** page in the Neon Console. Simply add the email account of the user you want to share your project with. Projects can be shared with any Neon user, including Neon Free Tier users. Usage is applied to the project owner's Neon account. For instructions, see [Share a project](/docs/manage/projects#share-a-project).
 - **Read replicas:** Neon's read replica feature enhances scalability and performance by allowing you to create read-only compute instances that operate on the same data as your read-write computes. With this feature, you can offload analytics or reporting queries, efficiently distribute read requests to achieve higher throughput, or provide read-only data access to certain users or applications. For more information, see [Read replicas](/docs/introduction/read-replicas).
 
 ### Added support

content/docs/manage/overview.md

@@ -2,7 +2,7 @@
 title: Overview of the Neon object hierarchy
 enableTableOfContents: true
 isDraft: false
-updatedOn: '2023-10-07T10:43:33.419Z'
+updatedOn: '2023-11-02T17:14:39.702Z'
 ---
 Managing your Neon project requires an understanding of the Neon object hierarchy. The following diagram shows how objects in Neon are related. See below for a description of of each object.
 
@@ -36,7 +36,7 @@ Neon account
 
 ## Neon account
 
-This is the account you used to sign up with Neon. Neon currently supports signing up with GitHub, Google, or partner accounts.
+This is the account you used to sign up with Neon. Neon supports signing up with an email, GitHub, Google, or partner account.
 
 ## API keys
 

content/docs/manage/projects.md

@@ -25,7 +25,7 @@ When you add a new project, Neon creates the following resources by default:
 - A primary branch called `main`. You can create child branches from the primary branch or from any previously created branch. For more information, see [Manage branches](/docs/manage/branches).
 - A single read-write compute endpoint. This is the compute instance associated with the branch. For more information, see [Manage computes](/docs/manage/endpoints).
 - A ready-to-use database, called `neondb`, which lives in the project's primary branch.
-- A default Postgres role that takes its name from your Neon account (the Google, GitHub, or partner account that you registered with).
+- A default Postgres role that takes its name from your Neon account (the email, Google, GitHub, or partner account that you registered with).
 
 ## About the Settings page
 

content/docs/manage/roles.md

@@ -4,10 +4,10 @@ enableTableOfContents: true
 isDraft: false
 redirectFrom:
   - /docs/manage/users
-updatedOn: '2023-11-02T10:54:40.458Z'
+updatedOn: '2023-11-02T17:14:39.703Z'
 ---
 
-In Neon, roles are Postgres roles. Each Neon project is created with a default Postgres role that takes its name from your Neon account (the Google, GitHub, or partner account that you registered with). This role owns the ready-to-use database (`neondb`) that is created in your Neon project's primary branch.
+In Neon, roles are Postgres roles. Each Neon project is created with a default Postgres role that takes its name from your Neon account (the email, GitHub, Google, or partner account that you registered with). This role owns the ready-to-use database (`neondb`) that is created in your Neon project's primary branch.
 
 Your default Postgres role and roles created in the Neon console, API, and CLI are granted membership in the [neon_superuser](#the-neon_superuser-role) role. Roles created with SQL from clients like [psql](/docs/connect/query-with-psql-editor), [pgAdmin](https://www.pgadmin.org/), or the [Neon SQL Editor](/docs/get-started-with-neon/query-with-neon-sql-editor) are only granted the basic [public schema privileges](/docs/manage/database-access#public-schema-privileges) granted to newly created roles in a standalone Postgres installation. These users must be selectively granted permissions for each database object. For more information, see [Manage database access](/docs/manage/database-access).
 

content/docs/reference/compatibility.md

@@ -3,7 +3,7 @@ title: Postgres compatibility
 enableTableOfContents: true
 redirectFrom:
   - /docs/conceptual-guides/compatibility
-updatedOn: '2023-10-19T23:10:12.858Z'
+updatedOn: '2023-11-03T11:49:30.943Z'
 ---
 
 Neon is protocol and application-compatible with Postgres. However, when using the Neon cloud service, there are some limitations that you should be aware of.

content/docs/reference/glossary.md

@@ -4,7 +4,7 @@ enableTableOfContents: true
 redirectFrom:
   - /docs/conceptual-guides/glossary
   - /docs/cloud/concepts/
-updatedOn: '2023-11-02T10:54:40.459Z'
+updatedOn: '2023-11-02T17:14:39.704Z'
 ---
 
 ### Access token
@@ -231,7 +231,7 @@ A usage-based paid plan offered by Neon. See [Neon plans](/docs/introduction/pla
 
 ### Neon user
 
-The user account that registers and authenticates with Neon using a GitHub or Google account. After authenticating, a Neon user account can create and manage projects, branches, users, databases, and other project resources.
+The user account that registers and authenticates with Neon using an email, GitHub, Google, or partner account. After authenticating, a Neon user account can create and manage projects, branches, users, databases, and other project resources.
 
 ### NeonVM
 

content/docs/unused/concepts-deprecated

@@ -9,7 +9,7 @@ redirectFrom:
 
 A Neon user is identified by their email address.
 
-A user registers and authenticates in Neon Web UI with their GitHub or Google account. More authentication methods are coming soon.
+A user registers and authenticates in Neon Web UI with their email, GitHub, Google, or partner account.
 
 After authenticating, a user can create and access [Projects](#project) and [query Project data](/docs/get-started-with-neon/tutorials#query-via-ui). You can also manage [Postgres Users](#postgres-users) and [Databases](#postgres-databases) in each Project.