You will need the Full Write App permission. Your campus or organization limit decides where it reaches, and different actions need different reach, as set out under Who can do what below. Your subscription also needs the App Builder add-on, and with more than one organization, an organization needs an App Builder seat to have versions of its own.
A version is a complete copy of your app design. It holds every screen, every block on those screens, and the navigation menu. You can keep as many versions as you like.
Versions are what let you work on a change in private. Build it in a version nobody can see, look it over, then make it live when it is ready.
Who sees which version
The version everyone sees by default is called the base. If your account has more than one campus or organization, you can also show a different version to a particular organization or campus. A person sees the first of these that applies:
A signed-in member sees the version for their Campus Attended, when that campus is in the organization being shown.
Otherwise, they see the version for the organization being shown.
Otherwise, they see the base.
A guest who is not signed in sees the organization's version, otherwise the base.
Seats. Organization and campus versions count only if the organization holds an App Builder seat. Without one, the organization shows the base, and its version choice is kept for when a seat is added.
An organization holds a seat when one is assigned to it, or when it has Branded App, which includes App Builder.
During a trial, every active organization holds App Builder. A trial never includes Branded App.
With one organization, the App Builder add-on or a trial covers everyone.
If you choose a version for an organization with no seat, you see: [Organization] has no App Builder seat. Assign one under Account Settings > Organizations. How do add-on seats work? explains seats.
Working with versions
Versions are managed at Mobile App > Builder. The Version drop-down at the top of the canvas chooses which version you are looking at, and everything below it belongs to that version. The designer lists only the versions you are allowed to edit, and opens on the base, otherwise the first version in the list.
If your account has one campus and one organization, the version that is live shows a green Published badge, and every other version shows an amber Publish this version button instead. With more than one campus or organization, you choose who sees each version on the Publishing tab instead (see below).
Add New and Copy do different things
Both create a new version, and the difference catches people out more than anything else in this area.
+ Add New - creates an empty version. It has no screens and no menu. Use it when you want to design the app over again from nothing.
Copy - duplicates the version you are viewing, with every screen and the whole navigation menu. Use it when you want to change something about a design you already have.
Tip: If you are trying out a change to the app your members already use, Copy is almost always the one you want. Copy the version that is live, make your changes in the copy, and publish it when you are happy with it.
Renaming and deleting a version
The three-dot menu beside the Version drop-down holds the actions for the version you are viewing:
Copy - creates a duplicate of this version.
Rename - changes the version's name. The name is only ever seen by your staff, so name versions in a way that tells you what is in them.
Delete - removes the version and everything in it.
A version that is in use, as the base or by any organization or campus, cannot be deleted or archived. You see: This version is in use. Choose another version wherever it is used first: followed by where it is used. Show a different version there first, then delete it.
The owning organization
Every version has one owning organization.
An organization or campus can show only versions its organization owns. The base can show any organization's version.
A version can move to another owner only while it is unused, or used only as the base.
Who can do what
Full Write App is needed for everything here, but how far it has to reach depends on the action:
Action | Full Write App needed at |
Edit a version | Any campus of the version's owning organization |
Delete or archive a version, or move it to another owner | Every campus of the owning organization |
Change or publish the base | Every campus of every active organization |
Note: Publishing the base is a whole-account action. Someone limited to some campuses or organizations can edit their own organization's versions but cannot change what everyone sees by default.
Publishing a version
Publishing is how a version becomes the design your members see. Publishing a version makes it the base. How you do that depends on your account.
With one campus and one organization
The builder shows the Publish this version button only when your account has neither more than one campus nor more than one organization. Only one version is published at a time, so publishing a version also takes the previous one out of the app.
Select the version you want to make live in the Version drop-down.
Click Publish this version beneath the drop-down.
Read the confirmation. It reads This will make the selected version live. The previously published version will revert to Unpublished.
Click Publish to go ahead, or Nevermind to back out.
The version that was live is not deleted. It moves back to unpublished and stays in the list, so you can publish it again if you need to undo the change.
With more than one campus or organization
Use the Publishing tab instead of the Publish this version button. It sets which version is the base, and which version each organization or campus shows. An account with one organization and several campuses sees this as a Who Sees Which Version panel.
The tab tells you when something stops a choice from taking effect:
Add an App Builder seat for [organization] to give it its own version.
The app is off for [organization]. It is left out of search and the Switch organization list, and its branded app can't be opened.
What One Church checks before publishing
Publishing checks the whole version, not only the screen you were last working on. A version newly shown to anyone must pass these checks:
One screen is set as the home screen.
Every menu item, button and list item points at a screen or form that still exists.
Every icon used in the navigation menu is one the app supports.
Every Web URL screen has a web address filled in.
Archived versions cannot be shown. If something does not pass, a red banner appears naming what needs attention. Fix the items it lists, then publish again.
Editing a version that is live
You can edit a version that members are already seeing, and the builder tells you when you are: a banner reads You are editing the live, published design. Changes appear in the app immediately.
Warning: Changes you save on a live version reach members straight away. There is no separate step to release them. If you want room to experiment, copy the live version first and work in the copy.
What publishing does not do
Publishing does not submit anything to the Apple App Store or Google Play. Your app is already in the stores, and the design inside it is what changes.
Publishing happens right away. There is no way to schedule a version to go live later, so publish at the moment you want members to see it.
Publishing does not change the app's name or icon. Each version's settings hold its colors, loading screen, pre check-in and barcode, while the icon and home banner stay those of the organization being shown.
Tip: After publishing, close and relaunch the app on a phone to see the new design. An app left open in the background can keep showing the previous one.







