Multi-campus (Plus): workspaces, campaigns, and schedules

Most teams use Communicate as a single location: there is one workspace context, one kind of campaign, and no “Global vs campus” language in the product.

Multi-campus mode is different: it adds workspaces (Global vs a named campus), global vs campus-owned campaigns, branched campus schedules on global campaigns, and team access choices (organization-wide vs specific campuses). This guide explains when that mode applies and how day-to-day work changes.

For core concepts, see Campaigns, Communications, the Calendar, and Admin Console.

Video overview

See multi-campus in action on the Plus plan.

This tutorial walks through Communicate’s multi-campus features. Topics include:

• The difference between Global and campus workspaces
• How Global campaigns and Campus campaigns work
• How to assign campuses to a Global campaign
• How campus schedules branch from a Global schedule
• Different ways to create campus versions of communications
• How schedule locking works
• Multi-campus campaign management
• Team permissions and campus access

Whether your campuses operate independently or coordinate communications centrally, this overview will help you understand how multi-campus works inside Communicate and how to choose the workflow that fits your church.

1. When multi-campus behavior appears

Default (single-campus experience)
If your organization is not on the Plus plan, or Plus is active but multi-campus has not been turned on, or it is on but you have not finished setup (for example, only one campus exists and Global coordination is not in play yet), the app behaves like a single campus:

• No Global workspace in the top navigation.
• No global vs campus campaign chrome (list row stripes, header scope badges, “Global Campaign” vs campus-owned labels).
• No Global Schedule / campus schedule tabs or Campus Schedule branching on campaigns.
• Sidebar Campuses may be hidden or show only setup/activation until multi-campus is fully in use—see your permissions and plan.

When multi-campus is fully active (Plus)
Multi-campus behavior appears when both are true:

1. Your organization is on Plus, and
2. Multi-campus is enabled for the tenant (the flag your Owners/Admins turn on in setup—not automatic just because you upgraded).

Plus alone is not enough. Until multi-campus is enabled, the product still behaves like single-campus usage—even on Plus. With only one campus after enablement, many Global coordination features (for example branching campus schedules) stay limited until you add another campus; global members may still see Global in WORKSPACE depending on their current selection.

Membership vs product mode
“Global access” for people (who can open the Global workspace and act on global-owned items) only matters when multi-campus is on. Owners and Admins are always organization-wide when multi-campus is on. Managers, Editors, and Viewers can be organization-wide or limited to specific campuses (see Admin Console and §12 below).

Short line for training: Global is shared across campuses. Campus is specific to one location.

2. Visual language (when multi-campus is active)

• Global: blue styling, globe icon, label Global.
• Campus: gray styling, map icon, label Campus or the campus name.
• Campaign list: a colored stripe on each row indicates global (blue) vs campus-owned (gray).
• Campaign page: background and header scope badge (for example Global Campaign vs {Campus name} Campaign). When multi-campus is off, this extra chrome does not appear.

3. Workspace (top navigation)

For a short overview of WORKSPACE, Global, and campus names (who sees what and when), see Workspace (Global and campus).

Where: Top navigation — control labeled WORKSPACE with the current environment name. Opening it shows Switch workspace with Global first (when you are allowed to use it), then each campus in sort order.

Persistence: Your choice is saved per user so you return to the same workspace.

Who sees Global

• Only people with organization-wide (global) membership see Global in the switcher when multi-campus is on.
• Campus-limited teammates never get Global. If they have one assigned campus, the control can collapse to a static campus name (no dropdown). If they have several, they switch between those campuses only.

Single campus in the org (multi-campus on): The workspace may be pinned to that campus—no Global row until there are multiple campuses.

While switching: Expect a short loading transition; sidebar content may dim briefly.

4. What the workspace changes day to day

Campaigns list

• Campus workspace: The list is filtered to campaigns tied to that campus (global campaigns that include that campus, plus campus-owned campaigns for that campus).
• Global workspace: All campaigns you are allowed to access.
• With multi-campus on, the list View menu (section Campaigns) toggles Global and Campus campaign types. You can show either, both, or neither—if both are off, the table is empty by design.
• Bulk edit/delete only applies to rows you are allowed to change in the current workspace (for example, global campaigns are not bulk-edited from a campus workspace).

Campaign detail

• Global campaign in Global workspace: Full edit (within your role), including an editable list of participating campuses where the product allows it.
• Global campaign in Campus workspace: You can open the campaign if it includes that campus, but campaign fields are read-only (you do not edit title, color, dates, etc. from campus context for global-owned campaigns).
• Campus-owned campaign: Editing is allowed when the current workspace campus matches that campaign’s campus (and your role allows). The wrong campus shows messaging that the campaign is not part of the current campus workspace.
• Archived campaigns: existing archive behavior still applies.

Calendar

• Global communications can be dragged, edited, or deleted only when you have global membership and you are in the Global workspace.
• In a campus workspace, global communications may be visible but interaction is locked for those rows. Campus-scoped users cannot mutate globals here.

Timeline

• Global campaigns: Drag and resize is disabled for campus-scoped users and for anyone while in a campus workspace—even if they normally have global membership. Campus-owned campaigns follow the usual timeline rules for your role.

5. Global vs campus campaigns

Creating

• Sidebar New → Create:
  • Global workspace + multi-campus on: New Global Campaign and New Campus Campaign (plus New Template when templates are available).
  • Otherwise: a single New Campaign path; ownership follows workspace and role rules in the modal.
• Modal titles: New Campaign (multi-campus off), New Global Campaign, New Campus Campaign (when those paths exist).
• Global workspace + multi-campus on + global membership: An optional Type control—Global vs Campus. Campus forces one campus in the picker. Global can attach to multiple campuses (subject to validation and in-app helper text—for example, saving a global campaign as draft when coordination across campuses is not ready yet).
• Campus workspace: New campaigns default to campus ownership; the campus is prefilled from the workspace.
• Campus-limited user in Global workspace: They cannot pick global ownership; flows behave like campus campaigns.

6. Global vs campus communications

• Inside a global campaign: New communications default to global scope in the Global workspace; in a campus workspace they default to campus scope for that workspace.
• Campus-owned campaign: Communications stay campus-scoped (the product prevents invalid global scope).
• Communication editor: When multi-campus is on, the linked campaign shows a small Global or Campus badge on the link chip.
• Global communications can show a campus assignment strip: which campuses the row applies to, with remove controls when editing is allowed—used for targeting before branch copies exist.

7. Communication schedule on a global campaign (tabs, branching, options)

Applies when: Multi-campus is on, the campaign is global (centrally owned), and multiple campuses participate. Campus-owned campaigns use a simpler schedule strip (no Global / branch tabs).

Tab strip

• Global Schedule tab — authoritative global communications (globe icon, blue tab styling). Holds the campaign schedule lock when your role allows (see §9).
• One tab per campus schedule — map styling; label is the campus name. × on a tab removes that campus’s branched schedule (with confirmation).
• Campus Schedule (with a + icon) — adds a branch; tooltip: Create a campus schedule for this campaign. If the schedule is locked, tooltips cite Schedule is locked. If the org only has one campus, messaging explains that Global coordination needs multiple campuses.

Create a campus schedule? modal

• Explains that campus schedules let teams customize locally while staying tied to the global campaign.
• Campuses: multi-select (or a fixed campus for campus-limited users).
• Initial content: Start with an empty campus schedule, or Copy all communications from Global Schedule.
• Primary action: Create schedule.

Unified layout (for example, campus workspace on a global campaign): Tabs can collapse into one combined view; Campus Schedule still creates or opens branches; lock appears where permitted.

View (schedule toolbar)

• Toggles Other campaigns and Event dates (same idea as elsewhere in Communication Schedule). Bulk actions that need the global surface still expect you to use the Global Schedule tab when tabs are shown.

Selection mode (Select)

• Enables Select All, Delete, status bulk actions, and—on the Global Schedule surface—a Campus Schedule action to copy selected global rows into a campus schedule (see §8).

8. Copying global communications into a campus schedule

Bulk: Selection mode on Global Schedule → Campus Schedule. The control is disabled with tooltips when you are on the wrong tab, nothing is selected, there is no valid campus, the schedule is locked, or a row already has a campus version.

Per-row flows follow the same guardrails (including locks).

Create campus version? / Create campus versions? modal

• Explains a separate version in the campus schedule stays connected to the global campaign.
• Lists the communication(s) (preview may cap with “+ N more”).
• Campus picker (one target campus per run).
• Optional: Remove this campus from the global communication — if left unchecked, the campus stays on both the global row and the new campus copy.

After deleting a campus schedule: If globals could have that campus reattached, a confirm step can offer Global communication handling: add the campus back to originals vs leave assignments as-is.

9. Locks: campaign schedule vs individual communication

Campaign schedule lock (on Global Schedule where tabs exist, and in other layouts when shown)

• Tooltip: control whether campus schedules and communication customization are allowed inside this campaign.
• Locked: Locked badge; branching (new campus schedule, copy-to-campus) is blocked; tooltips cite the lock.
• Who can still edit: Users with global membership in the Global workspace can still change global campaign structure as an organizational override, subject to role permissions. Others hit the same guards on bulk actions and edits.

Per-communication lock (on global communications when the control appears)

• If the campaign schedule is locked: every global communication is effectively locked for campus copying until the schedule is unlocked.
• When the schedule is unlocked: control whether campuses may copy and customize this row locally.
• Locked globals cannot be copied into a campus branch until unlocked (schedule lock overrides everything).

10. Sidebar: New, Campuses, and structure tools

New → Create (summary)

• Multi-campus on + Global workspace: New Global Campaign, New Campus Campaign, New Template (when available).
• Otherwise: New Campaign, New Template.

Campuses (map icon)

• Shown when you have campus.view permission and the multi-campus capability applies.
• Campus workspace: With multi-campus on, Campuses management is Global-workspace-only—the entry is hidden while you are in a campus workspace. If you open the panel in Global and then switch to a campus, the panel auto-closes.

Channels, Categories, and Colors remain permission-based, not workspace-gated like Campuses. For channel Delete (Global) vs Remove (campus opt-out with cascade confirm), see Channels.

11. Campuses side panel (add, edit, remove, order, primary)

When multi-campus is already on

• New adds a campus (name required; optional Set this campus as primary when no primary is set and multiple campuses exist).
• Each row: reorder (desktop drag handle), name, Primary star when set, ⋮ menu: Edit, Set as primary / Remove as primary, Delete.
• Delete is blocked if the campus is still assigned to any campaign (the error states that clearly).
• Primary campus is the labeled default for org-level UX.

When Plus includes multi-campus but it is not enabled yet

• The panel can show Is your church ready for multi-campus? with bullets (Plan by campus, Work globally when needed, Switch workspaces instantly, Control team access) and Get Started.
• Setup walks through Name your current campus, Add your other campuses, then Turn on multi-campus (or Keep one location to stay single-campus). You need at least two named campuses to turn it on.
• The first-login / church setup wizard may also enable multi-campus when Plus and two or more campuses are finalized (Owners / Admins for that wizard).

12. Roles and access scope (invite and member edit)

See User Permissions and Roles for roles, Organization-wide vs Specific campuses, Global access, and Categories.

• Invite user — Admin Console → Team → Invite User; set Access when multi-campus is on.
• Edit member — Global access checkbox and Campuses list; Role definitions (ℹ️) in the edit modal.
• Who can change scope — Owner, or Admin with global access.

13. Branching and schedule actions — role note

• Campus-scoped users: only Manager, Admin, or Owner may use add campus schedule and related branching controls—not campus-scoped Editor or Viewer.
• Organization-wide users: branching eligibility follows the normal permission path for their role (Editors/Viewers are not blocked by that campus-manager rule alone; they are still limited by campaign edit rights, locks, etc.).

14. Quick cross-reference (where to look in the app)

Additional resources

• Workspace (Global and campus) · User Permissions and Roles · Campaigns · Communications · Calendar · Timeline · Admin Console · Glossary: Campus

For questions, contact [email protected].

Last updated: 2026-07-16