New auth model docs (#1620)

web/docs/advanced/apis.md

@@ -3,7 +3,7 @@ title: Custom HTTP API Endpoints
 ---
 
 import { ShowForTs, ShowForJs } from '@site/src/components/TsJsHelpers'
-import { Required } from '@site/src/components/Required'
+import { Required } from '@site/src/components/Tag'
 
 In Wasp, the default client-server interaction mechanism is through [Operations](../data-model/operations/overview). However, if you need a specific URL method/path, or a specific response, Operations may not be suitable for you. For these cases, you can use an `api`. Best of all, they should look and feel very familiar.
 

web/docs/advanced/deployment/cli.md

@@ -2,7 +2,7 @@
 title: Deploying with the Wasp CLI
 ---
 
-import { Required } from '@site/src/components/Required';
+import { Required } from '@site/src/components/Tag';
 
 Wasp CLI can deploy your full-stack application with only a single command.
 The command automates the manual deployment process and is the recommended way of deploying Wasp apps.

web/docs/advanced/deployment/manually.md

@@ -5,7 +5,7 @@ title: Deploying Manually
 import useBaseUrl from '@docusaurus/useBaseUrl';
 import AddExternalAuthEnvVarsReminder from './\_addExternalAuthEnvVarsReminder.md'
 import BuildingTheWebClient from './\_building-the-web-client.md'
-import { Required } from '@site/src/components/Required'
+import { Required } from '@site/src/components/Tag'
 
 We'll cover how to deploy your Wasp app manually to a variety of providers:
 

web/docs/advanced/email.md

@@ -4,7 +4,7 @@ title: Sending Emails
 
 import SendingEmailsInDevelopment from '../\_sendingEmailsInDevelopment.md'
 
-import { Required } from '@site/src/components/Required'
+import { Required } from '@site/src/components/Tag'
 import { ShowForTs, ShowForJs } from '@site/src/components/TsJsHelpers'
 
 # Sending Emails

web/docs/advanced/jobs.md

@@ -2,7 +2,7 @@
 title: Recurring Jobs
 ---
 
-import { Required } from '@site/src/components/Required'
+import { Required } from '@site/src/components/Tag'
 import { ShowForTs, ShowForJs } from '@site/src/components/TsJsHelpers'
 
 In most web apps, users send requests to the server and receive responses with some data. When the server responds quickly, the app feels responsive and smooth.

web/docs/advanced/links.md

@@ -2,7 +2,7 @@
 title: Type-Safe Links
 ---
 
-import { Required } from '@site/src/components/Required'
+import { Required } from '@site/src/components/Tag'
 
 If you are using Typescript, you can use Wasp's custom `Link` component to create type-safe links to other pages on your site.
 

web/docs/advanced/web-sockets.md

@@ -3,7 +3,7 @@ title: Web Sockets
 ---
 import useBaseUrl from '@docusaurus/useBaseUrl';
 import { ShowForTs } from '@site/src/components/TsJsHelpers';
-import { Required } from '@site/src/components/Required';
+import { Required } from '@site/src/components/Tag';
 
 Wasp provides a fully integrated WebSocket experience by utilizing [Socket.IO](https://socket.io/) on the client and server. 
 

web/docs/auth/_multiple-identities-warning.md

@@ -0,0 +1,6 @@
+:::caution Using multiple auth identities for a single user
+
+Wasp currently doesn't support multiple auth identities for a single user. This means, for example, that a user can't have both an email-based auth identity and a Google-based auth identity. This is something we will add in the future with the introduction of the [account merging feature](https://github.com/wasp-lang/wasp/issues/954).
+
+Account merging means that multiple auth identities can be merged into a single user account. For example, a user's email and Google identity can be merged into a single user account. Then the user can log in with either their email or Google account and they will be logged into the same account.
+:::

web/docs/auth/_read-more-about-auth-entities.md

@@ -0,0 +1 @@
+You can read more about how the `User` entity is connected to the rest of the auth system in the [Auth Entities](./entities) section of the docs.