Private Extension Publishing

Private Extension Publishing lets you decide who in your organization can publish private extensions with the Raycast CLI. Members who aren't allowed to publish see why when they try.

• All members: All members of your organization can publish private extensions with the Raycast CLI.
• Managers only: Only Managers can publish private extensions with the Raycast CLI. See Roles & Permissions for more information.
• No one: No one in your organization can publish private extensions with the Raycast CLI. Members can still make changes to an extension and open a pull request to its repository, so the changes can be merged and then published.

To learn how to build and publish a private extension, see the Publish a Private Extension guide.

Configure Private Extension Publishing

1. In Raycast Account Settings, navigate to Organization → Admin Controls
2. Open the Private Extension Publishing dropdown
3. Choose All members, Managers only, or No one

When Publishing Isn't Allowed

If a member who isn't allowed to publish runs npm run publish, the publish fails and the terminal explains why. For example, when Private Extension Publishing is set to No one, the terminal shows an error that names your organization and points to Admin Controls:

HTTPError: publishing failed (error: 422 - Publishing private extensions is turned off for <organization-name>.
A manager can turn it back on with Private Extension Publishing in Admin Controls:
raycast.com/settings/organizations/<org-slug>/admin-controls
(raycast.com/api/v1/versions RequestID: <request-id>))

To let members publish again, a Manager can change Private Extension Publishing in Organization → Admin Controls.