Skip to content

Build an app

Private apps for your own company

On this page

A private app is an app only your own company uses: a link to your internal tools, a script your IT team runs, a sync to a system nobody else has. It installs in your company like any app, on the normal consent screen, but Bizisy doesn't review it and never lists it, and it never says "Unreviewed draft".

What you need#

  • A Bizisy company where you are an owner or admin (signed in with the same email as your developer account).
  • A developer organization linked to that company: create one in the console (Organizations), then an owner or admin of the company links it in Integrations → Build apps → Link an organization you own. The studio walks you through it when you choose Private to .

A person can't own a private app: it belongs to the organization, so it keeps working when someone leaves the team.

Create one#

In the console, My apps → Create an app, then under Who can install it choose Private to . The studio asks only what an install needs: name, what it does, redirect URLs and webhooks. A description, category and screenshots are optional (Add a listing). Create & install in creates it; an owner or admin installs it from its page in Integrations.

From an assistant or a script, send visibility: "private_company" to developers.apps.create (or developers.apps.setup.create) with the organization as publisher_id; the manifest is the same as any app's.

How it differs from a public app#

Private appPublic app
Who installs itOnly the company its organization is linked toEvery company, once Bizisy approves a version
ReviewNeverEvery version that asks for more
ListedNever: not in the directory or BrowseIn the directory and Browse
What installsWhat you build now (no versions)The approved version (test installs use the draft)
Consent screen"Private app by · only for ""Reviewed by Bizisy"

Asking for more access later never applies silently: the install shows Wants more access in Integrations and an owner or admin allows it again on the consent screen.

If the company unlinks the organization (or the company closes), the app stops there: its tokens are refused and its webhooks wait, and both Integrations and the console say why. Linking the organization again, or making the app public, brings it back. Removing one developer from the organization changes nothing.

Make it public#

Who can install it → Make public (owners of the organization) turns it into a normal app: you can submit it for review, and once approved every company can install it. Until then, its install in your company carries on as a test install of your organization's draft. An app that was never submitted or listed can be made private again.

A private app moves only to another organization linked to the same company (transfer).

Something missing or wrong on this page? Write to hello@bizisy.com.

Developer docs