Build an app
Organizations and app owners
Every app has exactly one owner: you, or an organization of developers. Companies see the owner on every listing: "by your name" or "by organization". Your sign-in email is never public.
Your own apps#
Apps you create under Personal (the default in the console's top bar) are yours alone: nobody else sees or changes them, and their listings say "by your display name". Your public page lists them once one is approved; its website and support email are in Settings (with Personal selected). Change your display name in Account.
Organizations#
An organization is a team or a brand that owns apps together. Any developer can create one (up to 5) and belong to many. Choose it in the console's top bar: My apps, Members and Settings then show the organization's.
| Owner | Developer | |
|---|---|---|
| Create, edit, test and submit its apps; rotate their credentials; see installs | Yes | Yes |
| Install its drafts in your own sandbox, or in a company where you are an owner or admin | Yes | Yes |
| Delete or transfer an app | Yes | No |
| Invite and remove members, change roles, edit its name, logo, website and support email | Yes | No |
| Delete the organization | Yes | No |
Invitations go by email and are accepted in the console, signed in with that address (a new free developer account works). They are open for 14 days. An organization always keeps at least one owner. Each owner has up to 10 apps, and each developer creates at most 30 apps in all.
An organization can be deleted only when none of its apps are listed: transfer them or delete them first. Its unlisted apps are deleted with it.
Transferring an app#
An owner moves an app between owners from the app's page (Manifest → Owner → Transfer):
- from you to an organization you own,
- between two organizations you own, or
- from an organization you own to yourself.
The app keeps its client id, its versions and review state, its listing and every install; companies notice only the new "by" line. Members of the old organization lose access, and its draft stops working in their sandboxes and in the companies where they installed it. Its client secret keeps working unless you tick Also stop the current client secret (stop_secret): do that when people of the old owner saw it, then create a new one in Credentials. In the API: developers_apps_transfer (a dry run checks it first).
Verified by a company#
An organization can be linked to a Bizisy company. An owner or admin of the company who is also an owner of the organization (signed in with the same email) links it in Bizisy, Integrations → Build apps; or creates a new organization there, linked from the start.
- Its apps show Verified: company with the company's Bizisy address: the company vouches for them.
- Their drafts can be tested in that company, as well as in its developers' sandboxes.
- The company's owners and admins see its apps and its developers' names and roles. They can invite developers (not owners) and remove the ones they invited; its owners manage everyone else. In an organization the company created from Bizisy, the company manages all of its members.
- Unlinking (by the company) removes only the badge and draft testing in the company: the organization, its members and its apps stay as they are. Closing the company unlinks it too.
Members' names and emails are never shown on public pages: listings and owners' pages show the person's display name or the organization only.
Something missing or wrong on this page? Write to hello@bizisy.com.