> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mightynetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I manage OAuth applications?

> Create and manage OAuth applications for third-party integrations that authenticate users via OAuth 2.0 on your Mighty Network.

OAuth applications allow you to create client credentials for third-party applications that need to authenticate users via OAuth 2.0 on your Mighty Network. This is useful when you want to build custom integrations or allow external apps to access your Network's Headless API on behalf of your members.

<Note>
  OAuth applications are available on the [Scale Plan](https://docs.mightynetworks.com/for-hosts/meet-mighty/whats-included-in-the-mighty-networks-business-plan) and above.
</Note>

## Access OAuth applications settings

1. Go to **Admin** from the main navigation
2. Navigate to **Settings** > **OAuth Applications**

## Create a new OAuth application

<Steps>
  <Step title="Open the creation dialog">
    Click the **New OAuth Application** button.
  </Step>

  <Step title="Enter application details">
    Fill in the required fields:

    * **Application Name**: A descriptive name to identify the application (e.g., "Mobile App", "CRM Integration")
    * **Redirect URI**: The callback URL where users are sent after authorization. You can enter multiple URIs separated by newlines (e.g., `https://myapp.com/oauth/callback`)
  </Step>

  <Step title="Select scopes">
    Choose the permissions your application needs. Scopes are divided into two categories:

    **Host scopes** grant access to manage network-level content:

    * `host:read:network_events` — View events in the Network
    * `host:read:network_spaces` — View spaces in the Network
    * `host:read:network_members` — View members in the Network
    * `host:read:network_plans` — View plans in the Network
    * `host:read:network_posts` — View posts in the Network

    **Member scopes** grant access to member-level actions:

    * `read:posts` — View posts the user has created
    * `read:courses` — View courses and course progress
    * `read:search` — Search Network content on the user's behalf
    * `write:posts` — Create, edit, and delete posts on the user's behalf
    * `write:comments` — Create, edit, and delete comments on the user's behalf

    <Warning>
      Host scopes can only be authorized by users who are hosts on your Network. If a non-host user tries to authorize an application that requests host scopes, the authorization will be denied. Each scope is flagged as host-only or member-level in the application settings.
    </Warning>

    <Tip>
      You can query the full list of available scopes — including which ones are host-only — through the GraphQL API using the `availableOAuthScopes` field on the Network type. This is useful if you're building a dynamic OAuth configuration UI.
    </Tip>
  </Step>

  <Step title="Choose the client type">
    * **Confidential client** (checked by default): Use for server-side applications that can securely store a client secret
    * **Public client** (unchecked): Use for native or single-page applications where the client secret cannot be kept secure. Public clients require PKCE (Proof Key for Code Exchange) for security
  </Step>

  <Step title="Save the application">
    Click **Create**. Your application's **Client ID** and **Client Secret** are displayed on the application card.

    <Warning>
      Copy and securely store the **Client Secret** immediately. You can reveal it later, but treat it like a password — never expose it in client-side code or version control.
    </Warning>
  </Step>
</Steps>

## Which applications appear in settings

The OAuth Applications settings page only shows applications you've created. System-level integrations (such as Kit, Zapier, or MCP connections) are managed separately and don't appear in this list.

## View your OAuth applications

All registered OAuth applications are listed on the OAuth Applications settings page. Each application card displays:

* **Application name**
* **Client ID** — The public identifier used in OAuth flows (with a copy button)
* **Client Secret** — Displayed only for confidential clients (with reveal/hide and copy buttons)
* **Redirect URI** — The registered callback URL
* **Type** — Either "Confidential" or "Public (PKCE required)"
* **Scopes** — The permissions granted to the application

## Edit an OAuth application

1. Click the **pencil icon** on the application card you want to edit
2. Update the name, redirect URI, scopes, or client type
3. Click **Save**

## Delete an OAuth application

1. Click the **trash icon** on the application card
2. Confirm the deletion in the dialog

<Warning>
  Deleting an OAuth application is permanent and cannot be undone. Any integrations using this application's credentials will immediately stop working.
</Warning>

## Related resources

<CardGroup cols={2}>
  <Card title="API overview" icon="code" href="/for-hosts/analytics-and-integrations/does-mighty-networks-have-an-api">
    Learn about the Mighty Networks API.
  </Card>

  <Card title="SSO with OAuth 2.0" icon="key" href="/for-hosts/analytics-and-integrations/how-do-i-enable-sso-for-my-mighty-network">
    Set up single sign-on for your Network.
  </Card>
</CardGroup>