@workos/mcp-docs-server 0.1.0 → 0.2.0

package/.docs/organized/docs/integrations/slack-oauth.mdx

@@ -1,6 +1,6 @@
 ---
 title: Slack OAuth
-description: Learn how to set up OAuth with Slack.
+description: Learn how to set up OAuth with Slack
 icon: slack
 breadcrumb:
   title: Integrations
@@ -8,95 +8,99 @@ breadcrumb:
 originalPath: .tmp-workos-clone/packages/docs/content/integrations/slack-oauth.mdx
 ---
 
-# Introduction
+## Introduction
 
-To configure your global Slack OAuth integration, you'll need two pieces of information from WorkOS and two pieces of information from Slack.
+The Slack OAuth integration allows your users to authenticate using their Slack credentials through the "Sign in with Slack" flow.
 
-From **WorkOS**:
+The configuration process involves creating or configuring a Slack App and setting up OAuth permissions with the client credentials in your WorkOS Dashboard.
 
-- A **Redirect URI** specific to Slack. This is where Slack will redirect users after they authenticate.
-- The **Slack** provider toggled on in the WorkOS Dashboard.
+---
 
-From **Slack**:
+## What WorkOS provides
 
-- A **Client ID**
-- A **Client Secret**
+When setting up Slack OAuth, WorkOS provides one key piece of information that needs to be configured in your Slack App:
 
-Once you've finished configuration, users can authenticate into your application using their Slack accounts.
+- [Redirect URI](/glossary/redirect-uri): The endpoint where Slack will send authentication responses after successful login
 
----
+The Redirect URI is available in the [WorkOS Dashboard](https://dashboard.workos.com/). In the left navigation menu, select the **Authentication** tab and the **OAuth providers** sub-tab. Locate the **Slack** section.
+
+![The Slack OAuth section in the WorkOS Dashboard.](https://images.workoscdn.com/images/9c70cdb3-0b02-4529-919a-3d91235e78cf.png?auto=format&fit=clip&q=50)
+
+Click **Enable**. The **Slack OAuth** configuration dialog will open. Locate the **Redirect URI**.
 
-## What WorkOS Provides
+![Slack OAuth Redirect URI in the WorkOS Dashboard.](https://images.workoscdn.com/images/c7800ed9-c9b9-4893-8821-e3af465362c5.png?auto=format&fit=clip&q=50)
 
-Within the [WorkOS Dashboard](https://dashboard.workos.com/), under **Authentication**, locate the **Slack** integration. There, you'll find the **Redirect URI**. After Slack completes the OAuth flow, it sends users (along with an authorization code) back to this URI.
+The **Redirect URI** serves as the destination for authentication responses and must be configured in your Slack App's OAuth & Permissions settings.
 
 ---
 
-## What You'll Need
+## What you'll need
 
-To integrate Sign in with Slack, you must have:
+You will need to obtain two pieces of information from a Slack App:
 
-1. An existing [Slack App](https://api.slack.com/apps).
-2. Your app's **Client ID** and **Client Secret**, found under your Slack App's settings.
-3. The WorkOS **Redirect URI**, which you'll add in Slack's OAuth & Permissions settings.
-4. (Optional) A Slack workspace for testing or development before going live.
+- **Slack Client ID**: Application identifier from Slack
+- **Slack Client Secret**: Authentication secret for the application
+
+The following sections will guide you through creating or configuring a Slack App and generating these credentials.
 
 ---
 
-## 1. Create or Open Your Slack App
+## (1) Create or open your Slack App
+
+Navigate to the [Slack App management page](https://api.slack.com/apps).
+
+If you don't already have a Slack App, click **Create an App**, provide a name, and choose the development workspace where you'll test.
 
-![A screenshot of the Slack API portal showing the create new app button](https://images.workoscdn.com/images/127f704d-ce13-49e0-9d82-2ba123547e3e.png?auto=format&fit=clip&q=80)
+![The Slack API portal showing the create new app button.](https://images.workoscdn.com/images/127f704d-ce13-49e0-9d82-2ba123547e3e.png?auto=format&fit=clip&q=80)
 
-1. Navigate to the [Slack App management page](https://api.slack.com/apps).
-2. If you don't already have a Slack App, click **Create New App**, provide a name, and choose the development workspace where you'll test.
-3. Once created, open your new Slack App to configure it.
+Once created, open your new Slack App to configure it.
 
 ---
 
-## 2. Configure OAuth & Permissions
+## (2) Configure OAuth & Permissions
 
-![A screenshot of the Slack API portal showing where to configure your redirect URI](https://images.workoscdn.com/images/f0e7d586-a8e1-4a67-8c06-085dc4009b32.png?auto=format&fit=clip&q=80)
+In your Slack App's settings, go to **OAuth & Permissions** in the left-hand navigation menu.
 
-1. In your Slack App's settings, go to **OAuth & Permissions** on the left-hand sidebar.
-2. Under **Redirect URLs**, add the **Redirect URI** from the WorkOS Dashboard.
-3. Click **Save URLs** to confirm.
+Under **Redirect URLs**, add the **Redirect URI** from the WorkOS Dashboard.
+
+![The Slack API portal showing where to configure your redirect URI.](https://images.workoscdn.com/images/f0e7d586-a8e1-4a67-8c06-085dc4009b32.png?auto=format&fit=clip&q=80)
+
+Click **Save URLs** to confirm.
 
 Under **Scopes**, ensure you request the standard OpenID scopes (e.g., `openid`, `profile`, `email`), which Slack requires for Sign in with Slack using OIDC.
 
 ---
 
-## 3. Retrieve Slack Credentials
+## (3) Retrieve Slack credentials
+
+Still in your Slack App's settings, find your **Client ID** and **Client Secret**.
 
-1. Still in your Slack App's settings, find your **Client ID** and **Client Secret**.
-2. Copy both values, as you'll need to add them to WorkOS in the next step.
+Copy both values as you'll need them for the WorkOS configuration.
 
 ---
 
-## 4. Provide Slack Credentials to WorkOS
+## (4) Configure Slack credentials in WorkOS
 
-![Screenshot of the WorkOS dashboard showing how to enable Slack OAuth](https://images.workoscdn.com/images/df2c527f-73a9-443c-9117-8d0c80eb52ea.png?auto=format&fit=clip&q=80)
+Now that you have the **Slack Client ID** and **Slack Client Secret** from the previous steps, return to the [WorkOS Dashboard](https://dashboard.workos.com).
 
-1. In the [WorkOS Dashboard](https://dashboard.workos.com/), go to **Authentication** and scroll down to the **Slack** integration.
-2. Click **Edit**.
-3. Paste in the **Client ID** and **Client Secret** from your Slack App.
-4. Toggle **Enabled** on if it's not already.
-5. Save your changes.
+In the **Slack OAuth** configuration dialog, enable the integration. Paste the credentials from Slack into their respective fields in the WorkOS Dashboard.
 
-![Screenshot of the WorkOS dashboard with the Slack OAuth connection enabled](https://images.workoscdn.com/images/774bff39-e6cd-4535-aee9-778b1fa6dd8b.png?auto=format&fit=clip&q=80)
+![The WorkOS dashboard with the Slack OAuth connection enabled.](https://images.workoscdn.com/images/c9c7c0de-c1f1-4d73-8f68-1b415d3dc5cb.png?auto=format&fit=clip&q=50)
+
+Click **Save** to complete the configuration.
 
 ---
 
-## 5. Test Your Sign in with Slack Flow
+## Frequently asked questions
 
-Once you've configured everything:
+### How is the WorkOS Slack OAuth integration different from implementing regular Slack OAuth flow?
 
-1. In your application, initiate the OAuth flow for Slack by directing users to WorkOS, specifying `SlackOAuth` as the provider.
-2. WorkOS will redirect users to Slack's sign-in screen.
-3. After successful authentication, Slack returns users to the WorkOS redirect URI along with an authorization code.
-4. WorkOS finalizes the authentication, and your application receives the user's Slack profile information.
+It's the same Slack OAuth flow as you could build yourself, but it's encapsulated within WorkOS SSO. This means you don't need to build it yourself. In addition to Slack OAuth, you can use WorkOS SSO to support other identity providers, all with a single integration.
 
-You're now ready to authenticate users with Slack in your production or development environment.
+### What is the provider query parameter and how is it used in the Slack OAuth integration?
 
----
+You can use the `provider` query parameter in the [Get Authorization URL API endpoint](/reference/sso/get-authorization-url) to support Slack OAuth for any domain. The `provider` query parameter should be set to `SlackOAuth`.
+
+### What scopes are required for Slack OAuth?
 
-After completing these steps, your "Sign in with Slack" integration through WorkOS should be fully functional. If you need further guidance on scopes, token rotation, or JWT validation, see Slack's [Sign in with Slack documentation](https://api.slack.com/authentication/sign-in-with-slack) and the [WorkOS SSO documentation](/reference/sso).
+The standard OpenID scopes (`openid`, `profile`, `email`) are required for Sign in with Slack using OIDC. These scopes provide access to the user's basic profile information necessary for authentication.

package/.docs/organized/docs/integrations/supabase-authkit.mdx

@@ -0,0 +1,46 @@
+---
+title: Supabase + AuthKit
+description: Learn how to use AuthKit with your Supabase application.
+icon: supabase
+breadcrumb:
+  title: Integrations
+  url: /integrations
+originalPath: .tmp-workos-clone/packages/docs/content/integrations/supabase-authkit.mdx
+---
+
+## Introduction
+
+This guide outlines the steps to use WorkOS as a Supabase [third-party auth provider](https://supabase.com/docs/guides/auth/third-party/overview). This will allow you to authenticate users with AuthKit and use AuthKit access tokens to access Supabase's REST and GraphQL APIs in your app.
+
+## (1) Add a WorkOS third-party auth integration
+
+Configure a WorkOS integration in the [Supabase dashboard](https://supabase.com/dashboard/project/_/auth/third-party).
+
+![Supabase 3rd party auth dashboard](https://images.workoscdn.com/images/6494746d-f6d2-46a1-bf26-f4fe7370e12b.png?auto=format&fit=clip&q=50)
+
+Your issuer URL is:
+
+```txt title="WorkOS Issuer"
+https://api_workos_com/user_management/client_123456789
+```
+
+![Supabase WorkOS Connection dialog](https://images.workoscdn.com/images/e4d5c238-a217-4c9c-a955-a882074919bb.png?auto=format&fit=clip&q=50)
+
+## (2) Set up a JWT Template
+
+Supabase RLS policies expect a `role` claim in the access token that corresponds to a database role. WorkOS already adds a `role` claim corresponding to the user's role in an organization. Set up a JWT template in the WorkOS dashboard (Authentication → Sessions) so that the role works with Supabase:
+
+<CodeBlock title="JWT template" file="supabase-jwt-template-example" />
+
+We add a `user_role` claim so that your application can still determine the role assigned to that user.
+
+## (3) Pass the access token to Supabase APIs
+
+Pass in your WorkOS client ID and auth domain when initializing the [Supabase client library](https://supabase.com/docs/guides/auth/third-party/workos#setup-the-supabase-client-library).
+
+<CodeBlock
+  title="Supabase client library initialization"
+  file="supabase-init-client-library"
+/>
+
+That's it! Supabase will now accept the access tokens returned by AuthKit.

package/.docs/organized/docs/integrations/{supabase.mdx → supabase-sso.mdx}

@@ -1,16 +1,18 @@
 ---
-title: Supabase
-description: Learn how to use WorkOS with your existing Supabase applications.
+title: Supabase + WorkOS SSO
+description: Learn how to use WorkOS for SSO with your Supabase application.
 icon: supabase
 breadcrumb:
   title: Integrations
   url: /integrations
-originalPath: .tmp-workos-clone/packages/docs/content/integrations/supabase.mdx
+originalPath: .tmp-workos-clone/packages/docs/content/integrations/supabase-sso.mdx
 ---
 
 ## Introduction
 
-This guide outlines the steps to make WorkOS SSO connections available to your Supabase application. It will require a few changes to your existing Supabase application code.
+This guide outlines the steps to make WorkOS SSO connections available to your application using Supabase Auth. It will require a few changes to your existing Supabase application code.
+
+If you are wanting to instead use AuthKit with your Supabase application, check out our [Supabase + AuthKit guide](/integrations/supabase-authkit).
 
 ---
 

package/.docs/organized/docs/integrations/vercel-oauth.mdx

@@ -0,0 +1,120 @@
+---
+title: Vercel OAuth
+description: Learn how to set up OAuth with Vercel
+icon: vercel
+breadcrumb:
+  title: Integrations
+  url: /integrations
+originalPath: .tmp-workos-clone/packages/docs/content/integrations/vercel-oauth.mdx
+---
+
+## Introduction
+
+The Vercel OAuth integration allows your users to authenticate using their Vercel credentials.
+
+The configuration process involves creating an OAuth application in Vercel and configuring the client credentials in your WorkOS Dashboard.
+
+---
+
+## What WorkOS provides
+
+When setting up Vercel OAuth, WorkOS provides one key piece of information that needs to be configured in your Vercel OAuth application:
+
+- [Redirect URI](/glossary/redirect-uri): The endpoint where Vercel will send authentication responses after successful login
+
+The Redirect URI is available in the [WorkOS Dashboard](https://dashboard.workos.com/). In the left navigation menu, select the **Authentication** tab and the **Providers** sub-tab. Locate the **Vercel** section.
+
+![The Vercel OAuth section in the WorkOS Dashboard](https://images.workoscdn.com/images/fbd35719-bb0d-4ccc-a613-a63dc3ba97b5.png?auto=format&fit=clip&q=50)
+
+Click **Enable**. The **Vercel OAuth** configuration dialog will open. Locate the **Redirect URI**.
+
+![The Vercel OAuth configuration modal in the WorkOS Dashboard](https://images.workoscdn.com/images/648eb886-837f-4eb2-a366-6d6094187a5d.png?auto=format&fit=clip&q=50)
+
+The **Redirect URI** serves as the destination for authentication responses and must be configured in your Vercel OAuth application as the Authorization Callback URL.
+
+---
+
+## What you'll need
+
+You will need to obtain two pieces of information from a Vercel OAuth application:
+
+- **Vercel Client ID**: Application identifier from Vercel
+- **Vercel Client Secret**: Authentication secret for the application
+
+The following sections will guide you through creating an OAuth application in your Vercel account and generating these credentials.
+
+---
+
+## (1) Create the Vercel OAuth application
+
+Log in to your [Vercel account](https://vercel.com/login) and navigate to your team Settings tab.
+
+In the left navigation menu, scroll down to select **Apps**. Click **Create** to create a new application.
+
+![Vercel Apps page with Create button](https://images.workoscdn.com/images/1c5a34a7-64c1-42d1-b2e8-363b3e14a1be.png?auto=format&fit=clip&q=50)
+
+Choose a name for your app, optionally add a logo, and click Save.
+
+---
+
+## (2) Configure the Vercel OAuth application
+
+In the left navigation menu, ensure that the **General** tab is selected. Scroll down to the **Authorization Callback URLs** section, and enter the **Redirect URI** from the Vercel OAuth configuration in the WorkOS Dashboard. Click **Save**.
+
+![Configuring Redirect URI in Vercel](https://images.workoscdn.com/images/b9e526f1-099b-472b-9a46-e9504ae2c106.png?auto=format&fit=clip&q=50)
+
+In the left navigation menu, select the **Authentication** tab. In the **Client Authentication Methods** section, make sure that **client_secret_post** is selected.
+
+![Configuring Client Authentication Methods in Vercel](https://images.workoscdn.com/images/65baf589-746b-4b33-b648-36f1d8b57c5d.png?auto=format&fit=clip&q=50)
+
+In the left navigation menu, select the **Permissions** tab. In the **Scopes** section, enable the **openid**, **email**, and **profile** scopes to allow the application to read basic user profile information. Click **Save**.
+
+![Configuring Scopes in Vercel](https://images.workoscdn.com/images/7240cd69-de9b-4a20-9f1a-13ed6beaf825.png?auto=format&fit=clip&q=50)
+
+---
+
+## (3) Generate client credentials
+
+In the left navigation menu, select the **General** tab and view your Client ID in the **Details** section.
+
+![View Client ID in Vercel](https://images.workoscdn.com/images/fef2735e-9a66-47f0-a0d5-e6d402a3ae7d.png?auto=format&fit=clip&q=50)
+
+In the left navigation menu, select the **Authentication** tab. Scroll down to the **Client Secrets** section and click **Generate** to generate a new Client Secret.
+
+![Generate Client Secret in Vercel](https://images.workoscdn.com/images/72e4b918-80ec-4aa8-b54a-349ca6d3bff2.png?auto=format&fit=clip&q=50)
+
+Note the **Client ID** and **Client Secret** values as you'll need them for the WorkOS configuration.
+
+> **Important**: The Client Secret is only shown once. Make sure to copy and store it securely.
+
+---
+
+## (4) Configure Vercel credentials in WorkOS
+
+Now that you have the **Vercel Client ID** and **Vercel Client Secret** from the previous step, return to the [WorkOS Dashboard](https://dashboard.workos.com).
+
+In the **Vercel OAuth** configuration dialog, enable the integration. Paste the credentials from Vercel into their respective fields in the WorkOS Dashboard.
+
+![Entering Vercel Credentials in WorkOS Dashboard](https://images.workoscdn.com/images/ff653223-0ace-4f91-85f5-48e238e48666.png?auto=format&fit=clip&q=50)
+
+Click **Save changes** to complete the configuration.
+
+You are now ready to start authenticating with Vercel OAuth. If you are using AuthKit's [Hosted UI](/authkit/hosted-ui), a Continue with Vercel button will be added to your login page.
+
+If you are building your own authentication flows outside of AuthKit's hosted UI, you will use the `provider` query parameter in the [Get Authorization URL API endpoint](/reference/authkit/authentication/get-authorization-url) to support global Vercel OAuth for any domain. The `provider` query parameter should be set to `VercelOAuth`.
+
+---
+
+## Frequently asked questions
+
+### How is the WorkOS Vercel OAuth integration different from implementing regular Vercel OAuth flow?
+
+It's the same Vercel OAuth flow as you could build yourself, but it's encapsulated within WorkOS SSO. This means you don't need to build it yourself. In addition to Vercel OAuth, you can use WorkOS SSO to support other identity providers, all with a single integration.
+
+### What is the provider query parameter and how is it used in the Vercel OAuth integration?
+
+If you are building your own authentication flows outside of AuthKit's hosted UI, you can use the `provider` query parameter in the [Get Authorization URL API endpoint](/reference/authkit/authentication/get-authorization-url) to support global Vercel OAuth for any domain. The `provider` query parameter should be set to `VercelOAuth`.
+
+### What scopes are required for Vercel OAuth?
+
+The **openid**, **profile**, and **email** scopes are required to allow the application to read user profile information necessary for authentication. These scopes provide access to the user's basic profile data and email address.

package/.docs/organized/docs/integrations/vmware-saml.mdx

@@ -1,6 +1,6 @@
 ---
 title: VMware
-description: "Learn how to configure a connection to\_VMware via SAML."
+description: Learn how to configure a connection to VMware via SAML.
 icon: vmware
 breadcrumb:
   title: Integrations
@@ -81,7 +81,7 @@ Some VMware configurations use `user.ExternalId` instead of `user.objectGUID`. I
 
 With [identity provider role assignment](/sso/identity-provider-role-assignment), users can receive roles within your application based on their group memberships. To return this information in the attribute statement, map the groups in your identity provider to a SAML attribute named `groups`.
 
-> Finish role assignment set-up by navigating to the SSO connection page in the _Organization_ section of the [WorkOS Dashboard](https://dashboard.workos.com/). Create SSO groups by referencing the group IdP ID. Then, assign roles to these SSO groups so group members are automatically granted roles within your application.
+> Finish role assignment set-up by navigating to the SSO connection page in the _Organization_ section of the [WorkOS Dashboard](https://dashboard.workos.com/). Create SSO groups by referencing the IdP Group ID. Then, assign roles to these SSO groups so group members are automatically granted roles within your application.
 
 ---
 

package/.docs/organized/docs/integrations/workday.mdx

@@ -1,6 +1,6 @@
 ---
 title: Workday
-description: "Learn about syncing your user list with\_Workday."
+description: Learn about syncing your user list with Workday.
 icon: workday
 breadcrumb:
   title: Integrations

package/.docs/organized/docs/integrations/xero-oauth.mdx

@@ -1,6 +1,6 @@
 ---
 title: Xero OAuth
-description: Learn how to set up OAuth with Xero.
+description: Learn how to set up OAuth with Xero
 icon: xero
 breadcrumb:
   title: Integrations
@@ -10,74 +10,119 @@ originalPath: .tmp-workos-clone/packages/docs/content/integrations/xero-oauth.md
 
 ## Introduction
 
-To configure your global Xero OAuth setup, you’ll need three pieces of information: a [Redirect URI](/glossary/redirect-uri), a Xero Client ID, and a Xero Client Secret.
+The Xero OAuth integration allows your users to authenticate using their Xero credentials through the "Sign in with Xero" flow.
+
+The configuration process involves creating an OAuth application in Xero and configuring the client credentials in your WorkOS Dashboard.
 
 ---
 
 ## What WorkOS provides
 
-WorkOS provides the Redirect URI, an allowlisted callback URL. It indicates the location to return an authorized user to after both an authorization code is granted, and the authentication process is complete.
+When setting up Xero OAuth, WorkOS provides one key piece of information that needs to be configured in your Xero OAuth application:
+
+- [Redirect URI](/glossary/redirect-uri): The endpoint where Xero will send authentication responses after successful login
+
+The Redirect URI is available in the [WorkOS Dashboard](https://dashboard.workos.com/). In the left navigation menu, select the **Authentication** tab and the **OAuth providers** sub-tab. Locate the **Xero** section.
+
+![The Xero OAuth section in the WorkOS Dashboard.](https://images.workoscdn.com/images/ea385495-75f6-4357-b16a-97c1383bbc9b.png?auto=format&fit=clip&q=50)
 
-Open your [WorkOS Dashboard](https://dashboard.workos.com) and browse to the _Authentication_ section on the left hand navigation bar. Scroll down to the _Xero OAuth_ section and click _Configure_.
+Click **Enable**. The **Xero OAuth** configuration dialog will open. Locate the **Redirect URI**.
 
-In the modal, you’ll see the Redirect URI as well as the fields you’ll populate later with information from Xero. This URI will be used as part of the registration process later in the Xero developer settings page.
+![Xero OAuth Redirect URI in the WorkOS Dashboard.](https://images.workoscdn.com/images/75e4e68e-cf07-4277-8979-7cd81f82f68f.png?auto=format&fit=clip&q=50)
+
+The **Redirect URI** serves as the destination for authentication responses and must be configured in your Xero application's OAuth settings.
 
 ---
 
-## What you’ll need
+## What you'll need
+
+You will need to obtain two pieces of information from a Xero Developer application:
 
-In order to integrate you’ll need the Xero Client ID and the Xero Client Secret.
+- **Xero Client ID**: Application identifier from Xero
+- **Xero Client Secret**: Authentication secret for the application
 
-These are a pair of credentials provided by Xero that you’ll use to authenticate your application via the OAuth protocol. To obtain them:
+The following sections will guide you through creating an OAuth application in your Xero Developer account and generating these credentials.
 
 ---
 
-### (1) Create the Xero OAuth Application
+## (1) Create the Xero OAuth application
 
 Log in to your [Xero developer account](https://developer.xero.com) and create a new application.
 
-![A screenshot showing the Xero developer homepage.](https://images.workoscdn.com/images/58e9b3af-7442-45e7-8be2-cb1fa9ab39a2.png?auto=format&fit=clip&q=80)
+![The Xero developer homepage.](https://images.workoscdn.com/images/58e9b3af-7442-45e7-8be2-cb1fa9ab39a2.png?auto=format&fit=clip&q=80)
+
+In the top right corner, select **New app**. Fill out the form starting with the application name.
+
+![The Xero form to create a new OAuth application.](https://images.workoscdn.com/images/f78a99b4-f004-4437-9612-6d97ef49bf3d.png?auto=format&fit=clip&q=50)
+
+For the **Integration type**, select **Web app**.
+
+For **Company or application URI**, use your application's homepage URI.
+
+For **Redirect URI**, use the **Redirect URI** from the Xero OAuth configuration in the WorkOS Dashboard.
+
+![OAuth client credentials in the Xero application settings.](https://images.workoscdn.com/images/9a0c3175-3af3-4613-a9f9-c9e6851507fe.png?auto=format&fit=clip&q=50)
+
+Agree to Xero's Developer Platform Terms & Conditions and click **Create app**.
 
-In the top right corner, select _New app_.
+---
+
+## (2) Generate client credentials
 
-Fill out the form starting with the application name.
+On the next page, you will see the Xero **App details** for your new OAuth application. From the left navigation menu, navigate to the **Configuration** page.
 
-![A screenshot showing the Xero form to create a new OAuth application.](https://images.workoscdn.com/images/f78a99b4-f004-4437-9612-6d97ef49bf3d.png?auto=format&fit=clip&q=50)
+![OAuth client credentials in the Xero application settings before creating a client secret.](https://images.workoscdn.com/images/5ec780c3-c325-4455-992e-20727c39f8f9.png?auto=format&fit=clip&q=50)
 
-For the _Integration type_, select _Web app_.
+Select **Generate a secret** to create a client secret.
 
-For _Company or application URI_, use your application's homepage URI.
+![OAuth client credentials in the Xero application settings after creating a client secret.](https://images.workoscdn.com/images/58158b26-0854-496f-9ccc-660955735463.png?auto=format&fit=clip&q=50)
 
-For _Redirect URI_, use the Redirect URI from the Xero OAuth configuration modal in the WorkOS Dashboard.
+Copy the **Client ID** and **Client secret 1** as you'll need them for the WorkOS configuration.
+
+---
 
-![A screenshot showing OAuth client credentials in the Xero application settings](https://images.workoscdn.com/images/9a0c3175-3af3-4613-a9f9-c9e6851507fe.png?auto=format&fit=clip&q=50)
+## (3) Configure Xero credentials in WorkOS
 
-Agree to Xero's Developer Platform Terms & Conditions and click on _Create app_.
+Now that you have the **Xero Client ID** and **Xero Client Secret** from the previous steps, return to the [WorkOS Dashboard](https://dashboard.workos.com).
 
-### (2) Generate client credentials
+In the **Xero OAuth** configuration dialog, enable the integration. Paste the credentials from Xero into their respective fields in the WorkOS Dashboard.
 
-On the next page, you will see the Xero _App details_ for your new OAuth application.
+![OAuth client credentials in the WorkOS Xero setup modal filled with client id and client secret.](https://images.workoscdn.com/images/9bb1cd53-a5cc-4a04-b7d4-2fd9791ad499.png?auto=format&fit=clip&q=50)
 
-From the left sidebar, navigate to the _Configuration_ page.
+Click **Save** to complete the configuration.
+
+You are now ready to start authenticating with Xero OAuth. You will use the `provider` query parameter in the Get Authorization URL API endpoint to support global Xero OAuth for any domain. The `provider` query parameter should be set to `XeroOAuth`.
+
+---
 
-![A screenshot showing OAuth client credentials in the Xero application settings before creating a client secret](https://images.workoscdn.com/images/5ec780c3-c325-4455-992e-20727c39f8f9.png?auto=format&fit=clip&q=50)
+## Configure Additional OAuth Scopes (Optional)
 
-Select _Generate a secret_ to create a client secret.
+WorkOS will request the OAuth scopes that are required for authentication by default. You can optionally configure your integration to request additional OAuth scopes as needed.
+
+When the **Return Xero OAuth tokens** option is selected, the access token and refresh token from Xero will be included in the response from the [Authenticate with code API](/reference/authkit/authentication/code).
+
+![A screenshot showing Xero OAuth scopes configuration in the WorkOS Dashboard](https://images.workoscdn.com/images/a39beaaf-faf4-4fcf-98b7-eeb54f0135fb.png?auto=format&fit=clip&q=50)
+
+Any scopes configured here will be included on every Xero OAuth request. To specify additional scopes dynamically, use the `provider_scopes` query parameter on the [Get Authorization URL API endpoint](/reference/authkit/authentication/get-authorization-url).
+
+For more information, see Xero's OAuth scopes [documentation](https://developer.xero.com/documentation/oauth2/scopes).
+
+---
 
-![A screenshot showing OAuth client credentials in the Xero application settings after creating a client secret](https://images.workoscdn.com/images/58158b26-0854-496f-9ccc-660955735463.png?auto=format&fit=clip&q=50)
+## Frequently asked questions
 
-Copy the _Client ID_ and _Client secret 1_.
+### How is the WorkOS Xero OAuth integration different from implementing regular Xero OAuth flow?
 
-In the next step, you will provide both the Xero Client ID and Client Secret to the WorkOS dashboard.
+It's the same Xero OAuth flow as you could build yourself, but it's encapsulated within WorkOS SSO. This means you don't need to build it yourself. In addition to Xero OAuth, you can use WorkOS SSO to support other identity providers, all with a single integration.
 
-### (3) Provide client credentials to WorkOS
+### What is the provider query parameter and how is it used in the Xero OAuth integration?
 
-Go back to the _Authentication_ section in the WorkOS Dashboard, and click on _Edit_ under _Xero OAuth_.
+You can use the `provider` query parameter in the [Get Authorization URL API endpoint](/reference/sso/get-authorization-url) to support global Xero OAuth for any domain. The `provider` query parameter should be set to `XeroOAuth`.
 
-![A screenshot showing OAuth client credentials in the WorkOS Xero setup modal filled with client id and client secret.](https://images.workoscdn.com/images/64add3ff-91ac-4d1c-a5cc-3383762fb877.png?auto=format&fit=clip&q=50)
+### What type of Xero integration should I select?
 
-Toggle _Enabled_ on and provide the client credentials from Xero that you generated in the previous step.
+You should select **Web app** as the integration type when creating your Xero OAuth application. This is the correct type for OAuth integrations that will work with WorkOS.
 
-Finally, click _Save_.
+### Where can I find my Xero application after creation?
 
-You are now ready to start authenticating with Xero OAuth. Your users will see the option to sign-in with Xero when visiting your [AuthKit](/user-management) domain.
+After creating your Xero application, you can find it in your [Xero Developer Portal](https://developer.xero.com) under your apps list. From there, you can access the **Configuration** page to manage your OAuth settings and regenerate credentials if needed.

package/.docs/organized/docs/magic-link/example-apps.mdx

@@ -1,46 +1,46 @@
 ---
 title: Example Apps
-description: "View sample Magic\_Link\_apps for\_each\_SDK."
+description: View sample Magic Link apps for each SDK.
 originalPath: .tmp-workos-clone/packages/docs/content/magic-link/example-apps.mdx
 ---
 
-You can view minimal example apps that demonstrate how to use the WorkOS SDKs to authenticate users via Magic Link:
+You can view minimal example apps that demonstrate how to use the WorkOS SDKs to authenticate users via Magic Link:
 
 <ExampleApps.Root>
   <ExampleApps.Card
     href="https://github.com/workos/node-example-applications/tree/main/node-magic-link-example"
-    title="Node.js Magic Link app"
+    title="Node.js Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/typescript-example-applications/tree/main/typescript-magic-link-example"
-    title="TypeScript Magic Link app"
+    title="TypeScript Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/ruby-example-applications/tree/main/ruby-magic-link-example"
-    title="Ruby Magic Link app"
+    title="Ruby Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/python-flask-example-applications/tree/main/python-flask-magic-link-example"
-    title="Python Flask Magic Link app"
+    title="Python Flask Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/python-django-example-applications/tree/main/python-django-magic-link-example"
-    title="Python Django Magic Link app"
+    title="Python Django Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/go-example-applications/tree/main/go-magic-link-example"
-    title="Go Magic Link app"
+    title="Go Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/java-example-applications/tree/main/java-magic-link-example"
-    title="Java Magic Link app"
+    title="Java Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/php-example-applications/tree/main/php-magic-link-example"
-    title="PHP Magic Link app"
+    title="PHP Magic Link app"
   />
   <ExampleApps.Card
     href="https://github.com/workos/dotnet-example-applications/tree/main/dotnet-magic-link-example"
-    title=".NET Magic Link app"
+    title=".NET Magic Link app"
   />
 </ExampleApps.Root>

package/.docs/organized/docs/magic-link/index.mdx

@@ -7,6 +7,8 @@ showNextPage: true
 originalPath: .tmp-workos-clone/packages/docs/content/magic-link/index.mdx
 ---
 
+> **Deprecated:** Magic Link is not recommended due to issues with email clients or other security software visiting the links and invalidating them. Instead, use [Magic Auth](/authkit/magic-auth), which provides a more secure passwordless authentication method.
+
 ## Introduction
 
 Managing password authentication entails significant overhead for engineering teams and opens up many risks for breaches. Magic Link from WorkOS gives you the ability to build a secure passwordless authentication flow utilizing email. Send users a one-time-use link and let them sign in with a single click.