GITBOOK-82: change request with no subject merged in GitBook

proofzero · Jun 28, 2023 · 9525653 · 9525653
1 parent 66c0cdb
commit 9525653
Show file tree

Hide file tree

Showing 7 changed files with 33 additions and 0 deletions.
diff --git a/docs/.gitbook/assets/CleanShot 2023-06-28 at 13.30.13.png b/docs/.gitbook/assets/CleanShot 2023-06-28 at 13.30.13.png
diff --git a/docs/.gitbook/assets/Dropdown.png b/docs/.gitbook/assets/Dropdown.png
diff --git a/....gitbook/assets/No Data (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1).png b/....gitbook/assets/No Data (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (1).png
diff --git a/....gitbook/assets/No Data (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (2).png b/....gitbook/assets/No Data (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (2) (2).png
diff --git a/docs/CONTENTS.md b/docs/CONTENTS.md
@@ -15,6 +15,8 @@
 * [Adding Users to your Database](guides/connecting-to-your-database.md)
 * [Authenticating Users in your App](guides/authenticating-users-in-your-app.md)
 * [Setup with Supabase](guides/setup-with-supabase.md)
+* [Requesting Email](guides/requesting-email.md)
+* [Connected Accounts](guides/connected-accounts.md)
 * [Using Smart Contract Wallets](guides/using-smart-contract-wallets.md)
 
 ## Platform

diff --git a/docs/guides/connected-accounts.md b/docs/guides/connected-accounts.md
@@ -0,0 +1,2 @@
+# Connected Accounts
+
diff --git a/docs/guides/requesting-email.md b/docs/guides/requesting-email.md
@@ -0,0 +1,29 @@
+---
+description: Using the connected email scope
+---
+
+# Requesting Email
+
+This guide will walk you through how to request email addresses from your user using the Email [Scope](../reference/scopes.md).
+
+### Step 1
+
+In your application OAuth configuration make sure that email is selected in the "allowed scopes" dropdown. Make sure to save this configuration before moving to step 2.
+
+<figure><img src="../.gitbook/assets/CleanShot 2023-06-28 at 13.30.13.png" alt=""><figcaption><p>Email Scope Dropdown</p></figcaption></figure>
+
+### Step 2
+
+When [logging in users](../getting-started/auth-flow.md) make sure you add `email` to the `scope` query param. Your auth url should look something like this `https://<rollup.id or your custom domain>/authorize?client_id=xxx&state=xxx&scope=email`
+
+### Step 3
+
+After authenticating into your custom Rollup application, your users will we be presented with an authorization screen containing the email scope authorization request.
+
+If the user already as a connected email, this email will be automatically selected. If no email address is connected to their identity they can connect an new email address and continue.&#x20;
+
+<figure><img src="../.gitbook/assets/Dropdown.png" alt=""><figcaption><p>Email Authorization</p></figcaption></figure>
+
+### Step 4
+
+When redirected back to your application, the [access token](../advanced/tokens.md) will now contain an authorization for email address. The email address will also be available returned in the user token via the [user info endpoint](../reference/passport-api.md#user-info).