Zita Administration Guide

For Super Admins and Admins

Last updated: September 22, 2026

Introduction

This guide is for Admins and Super Admins responsible for the day-to-day management of your church in Zita. It picks up where the Zita Setup Guide left off.

This guide covers what’s not obvious from using the app — permissions, things that can’t be undone, and the handful of processes (data recovery, subscription/billing) that are rare enough or high-stakes enough to be worth reading before you need them. It doesn’t walk through routine tasks like adding a person or editing a service — those work the way you’d expect from tapping + and editing any record in Zita. If something doesn’t behave the way you expect, ask in the Facebook group.

If you haven’t completed setup yet, start with the Zita Setup Guide first. This guide assumes your church is already up and running.

The Two Admin Roles

For almost everything in this guide, Super Admin and Admin work identically. There are two exceptions: the Super Admin owns the church’s data and is the only person who can see the Billing tab and manage the subscription, and the Super Admin is the only person who can send invitations — Apple’s iCloud sharing only allows the account that owns the church’s data to add new participants. A church can have one Super Admin and up to 5 Admins.

A common pattern: a Liturgical Admin (typically clergy) who keeps the service calendar and clergy assignments accurate, and a Guild Admin (typically a parish administrator, secretary, or experienced guild lead) who maintains membership and guild structure. These don’t have to be different people.

Quick Reference

Tab Who Can See It What’s Here
Scheduling Everyone The main scheduling grid. Guild leads and admins make assignments; members self-schedule to roles they belong to. Mac toolbar has Share/Export to PDF.
Guilds Everyone (edit access varies) Per-guild Items (inventory), Guides, Members (roster), and Checklists. Guild leads manage their own guild’s; Admins manage any guild’s.
Admin → Services Admins and Super Admin Add, edit, deactivate services. Generate the annual calendar. Assign clergy and staff.
Admin → Service Types Admins and Super Admin Which roles, default times, and default Guides/Checklists apply to each kind of service.
Admin → Guilds Admins and Super Admin Guild structure, roles, slot counts. Add/remove members from roles, individually or via CSV import.
Admin → Clergy & Staff Roles Admins and Super Admin Add, rename, or deactivate clergy/staff roles themselves (not assigning people to them).
Admin → People Admins and Super Admin Add, edit, deactivate people. Set App Roles. Import from CSV. Sending invitations is Super Admin only.
My Info Everyone (own data only) Personal profile, guild memberships, upcoming assignments, calendar export, sub requests, unavailability.
Billing Super Admin only Current plan, active person count, subscription management, purchase restore.

Roles and Permissions

Action Super Admin Admin Guild Lead Member
Access Admin tab ✓ ✓ ✗ ✗
Access Billing tab ✓ ✗ ✗ ✗
Manage people ✓ ✓ ✗ ✗
Send invitations ✓ ✗ ✗ ✗
Manage guilds and roles ✓ ✓ ✗ ✗
Manage services and Service Types ✓ ✓ ✗ ✗
Assign clergy and staff ✓ ✓ ✗ ✗
Manage Guides/Checklists/Inventory for any guild ✓ ✓ ✗ ✗
Manage Guides/Checklists/Inventory for their own guild ✓ ✓ ✓ ✗
Schedule any guild ✓ ✓ ✗ ✗
Schedule their own guild ✓ ✓ ✓ ✗
Self-schedule to roles they belong to ✓ ✓ ✓ ✓
Mark others’ unavailability ✓ ✓ ✗ ✗

Guild Lead is a designation on a person’s record, not an App Role — a Guild Lead can also be Standard, Admin, or Super Admin. A person can belong to more than one church; a switcher near the top of each tab (window toolbar on Mac) appears once they do.

Things You Can’t Undo

  • Deactivating a person permanently clears all their future service assignments. Those slots go back to unassigned with no way to restore them. Past assignments and the person’s history are preserved, and they can be reactivated later — but their future schedule is gone the moment you deactivate them.
  • Removing someone from a guild role does the same — it immediately and permanently clears their future assignments in that role.
  • Unchecking a role from a Service Type immediately clears any upcoming assignments to that role on every service using that type. Past assignments are untouched. Deactivating a Service Type entirely reverts its services back to showing every active role, rather than leaving them stuck on a fixed, outdated set.
  • The annual service generator does not check for duplicates. Running it over a date range that overlaps existing services creates duplicates that have to be deactivated one by one. Always tap Preview before Generate, and double-check your date range.
  • Everything else is reversible. People, services, guilds, roles, and inventory items are deactivated, not deleted, and can be reactivated at any time.

Good to Know

  • Clergy assignments are private to Admins by design. Guild leads and members see a service’s mass type, vestment color, and time, but never who is assigned to celebrant, deacon, or other clergy/staff roles.
  • Active people count toward your subscription tier — keep the People list focused on those actually serving in a guild, clergy, or staff role, not your full parishioner directory.
  • Only the Super Admin can send or resend invitations — an Apple iCloud sharing restriction, not a Zita setting, so it can’t be delegated.
  • A church can have at most 5 Admins. Promoting a 6th requires first stepping an existing Admin back to Standard.
  • Guides, Checklists, and Inventory are guild-scoped — a guild lead manages them only for the guild(s) they lead.
  • Past Checklist history lives under Admin → Services → Past Services (open the service, scroll to Checklists), not under the Guilds tab.

Recovering a Previous Church’s Data

If your church has used Zita before — a new device, data loss, lost Super Admin credentials, or reinstalling — you don’t need to rebuild from scratch. Recovery works from a recovery file: a JSON export of your church’s guilds, roles, members, services, and inventory structure.

Getting a recovery file. Either export one now (Admin → Church Settings → Emergency Recovery → Export Recovery File, from any admin’s device with current access), or use an automatic one — Zita saves a recovery file automatically every 30 days on each admin’s device, and Admin → Church Settings shows a “Last Automatic Export” date so you can check whose is freshest.

Using it. During initial setup, the first (Church Details) screen has a “Recovering a church that previously used Zita?” link — choose it and select your file instead of starting fresh. Your guild/role structure, member and clergy/staff records, and roughly a year of service history come back.

What to know before you start:

  • Everyone comes back as they were at export time, but Admin access is not restored — everyone except the new Super Admin comes back as Standard, so re-designate Admins and guild leads afterward.
  • Recovery always creates a new subscription, starting on Free unless you upgrade. If the recovered church has more active people than the new plan allows, the extras aren’t dropped — they’re locked the same way an over-limit or lapsed subscription locks people (see Subscription and Billing, below).
  • Recovery does not carry over the previous iCloud share — everyone’s invite status resets to Not Invited, even people who were previously Linked, and needs to be re-sent from Admin → People.
  • Recovery is for churches with an existing Zita recovery file, not a general import tool. If you’re not sure recovery is the right move, use the Contact Us form before you begin.

After recovery, do a quick pass through Service Types, Guilds, People, and Services — the same review you’d do after a fresh setup — before inviting your team back in.

Subscription and Billing

Billing tab — Super Admin only.

Tier Active Person Limit Cost
Free 15 Free
Small 30 Monthly or annual
Medium 50 Monthly or annual
Large Unlimited Monthly or annual

A warning banner appears in Admin → People at 90% of your tier’s limit (14/15, 27/30, 45/50). At the limit exactly, adding new people is disabled until you deactivate someone or upgrade.

Auto-Renew status is visible to every admin (not just Super Admin) under Admin → Church Settings → Subscription. Turning auto-renew off doesn’t trigger any grace period on its own — the plan just stays active through its current paid period, then behaves like a lapse.

If a subscription lapses (a failed renewal after Apple’s own billing retry/grace period, or auto-renew running out), Zita never deactivates anyone. Instead it locks the overflow beyond your tier, in this priority order — earlier groups, and earlier joiners within a group, stay unlocked longest:

  1. Admins
  2. Clergy and Staff
  3. Guild Leads
  4. Regular Members

The Super Admin is never locked, under any circumstances. Locked people keep every guild membership and past/already-scheduled assignment, and can still sign in and see their own schedule — they just can’t be edited, newly assigned, or newly scheduled while locked. No one new can be added while the church is over capacity. A red banner appears for everyone while this applies; only the Super Admin sees a “View Plans” button on it. Upgrading, or manually deactivating enough people to fit, unlocks anyone who now fits — locking only ever happens from an actual lapse or an over-limit recovery import, never automatically in the other direction.

Restoring a purchase (e.g. after reinstalling): Billing tab → Restore Purchases, to re-sync entitlements from the App Store.

Common Questions

  • “I can’t see the Admin tab.” Guild leads don’t have Admin access by design. If they need to manage members, roles, or services, they need to be promoted to Admin (Admin → People → their record → App Role).
  • “Someone isn’t showing up in the assignment picker.” Either they aren’t assigned to that role yet (Admin → Guilds), or they’re locked (see Subscription and Billing, above).
  • “The wrong mass type/vestment color is showing for a service.” That’s a service detail correction — only Admins can edit services (Admin → Services).
  • “A guild lead got a sub-request email for a role they don’t personally fill.” Expected — sub-request emails always go to the guild’s lead(s) so they know a slot opened, even for roles the lead isn’t eligible for themselves.
  • “A member wants their unavailability recorded but they don’t use the app.” Admins can add it on their behalf: Admin → People → their record → Unavailability. Guild leads can only mark their own.

For initial church setup, see the Zita Setup Guide. For questions not covered here, ask in the Facebook group or use the Contact Us form.