Publishing and versions

Publishing fixes an app's pages, definitions, and actions. New memory keeps flowing through the published version.

Publishing an app for the first time

A published app is billed, so its first publication needs an Owner or Admin.

• An Owner or Admin can publish any app directly.
• A steward who is not an Owner or Admin submits one revision for approval, with an optional note.

A submission works like this:

1. The steward submits a specific revision.
2. Owners and Admins see it under Waiting for approval and get an in-app notice.
3. An Owner or Admin approves or rejects it. A rejection carries a reason.

Approval publishes exactly the revision that was submitted. Later drafts do not change what the reviewer approves.

One submission can be pending for each app. Submitting a newer revision replaces it, and the steward can withdraw it. If the submission was replaced or withdrawn before the review, the approval fails and nothing changes.

Publishing fails if:

• the specification is not valid;
• any definition is unconfirmed; or
• a source the app reads is not connected.

Publishing also fails if someone else published first. Reload and publish again.

Later releases

Once an app is published, a new release does not change the bill. The steward, an Owner, or an Admin publishes it directly, with no approval.

Audiences

Audience	Who can open the published app
By invitation only	The steward, Owners, Admins, and the members invited to it
Everyone	Every active member of your team

An app starts as by invitation only, with nobody invited.

The steward, an Owner, or an Admin can switch the audience and change the invitations at any time in the app's settings. Neither needs approval, because neither changes the bill.

Only active members of your team can be invited. A newly invited member gets an in-app notice. Members who are not invited cannot see that a by-invitation app exists.

Revisions and releases

• A revision is one saved specification. Revisions are never edited. Each change creates a new one.
• A release is a revision that was published. Releases are numbered in order.

The Versions page of an app lists its revisions, releases, and review decisions.

Rollback

Rolling back publishes an earlier release again as a new release. History is never rewritten.

Stewards

The member who builds an app is its steward. If the steward leaves the team, the app and its history stay. An Owner or Admin can reassign the steward in the app's settings.

Archiving

An archived app no longer runs and is hidden from the default list. Its versions and history are kept.