Release

Make your connector available to end-users — either globally or for specific accounts.

Once your connector is synced to production, you need to make it available to end-users. There are two ways: enable access for specific entities, or release globally.

Enable access

Use Change access to make the connector available to specific accounts, projects, or sites. This is the right choice when:

The connector is intended for specific customers

You want a staged rollout — test with a few accounts before going wide

The connector is for internal use only

You can grant and revoke access at any time. Each entity you enable must be in the connector's target scope (configured during sync to prod).

Release globally

Use Release to make the connector available to all users on the Productsup platform. This is the right choice when the connector is ready for general use.

Releasing globally clears all specific access grants. If you previously enabled access for specific accounts, projects, or sites, those lists are reset when you release. This is a one-way transition — if you need to go back to limited access, you'll need to unrelease first and then re-enable specific access.

Unreleasing

You can unrelease a connector to remove it from global availability. After unreleasing:

The connector is no longer visible to new users

Previously granted specific access is not restored — you need to re-enable access manually

Sites that already have the connector assigned continue to work

Prerequisites

Before you can release or enable access, the connector version must:

Be synced to production

Have a platform connector ID (created during the sync process)

Summary

Action	Scope	When to use
Change access	Specific accounts, projects, or sites	Internal connectors, staged rollouts, customer-specific connectors
Release	All platform users	Connector is ready for general availability
Unrelease	Removes global availability	Need to pull back a released connector