---
title: Publish
subtitle: Make your OAuth app public and get listed in the Close Integrations Directory.
slug: /integrations/publish
---

## Private vs. public apps

OAuth apps are **Private** by default, meaning only members of your own Close organization can authorize them. This is fine if you and your teammates are the only users.

If you want _any_ Close user to be able to authorize your app, you need to make it **Public**.

## Making your app public

1. Go to [**Settings** → **Developer** → **OAuth Apps**](https://app.close.com/settings/developer/oauth-apps) and select your app.
2. Click **Make Public** and submit for review.
3. We'll review your app and reply by email.

Once approved, your app will be marked as Public and any Close user will be able to authorize it.

## Getting listed in the Integrations Directory

After your app is public, you can apply to have it listed in the [Close Integrations Directory](https://close.com/integrations/) — making it discoverable by thousands of Close customers and linking directly to your product.

### Requirements

- Your integration must be publicly available (not internal-only).
- It must use [OAuth 2.0](/integrations/create-an-oauth-app) for authentication (not API keys).
- It should provide clear value to Close users.

### How to apply

Email [support@close.com](mailto:support@close.com?Subject=Integration%20Listing%20Request) with:

- Your integration name and description
- A link to your product
- A brief explanation of what it does with Close
- Your OAuth App's Client ID