For customers that operate across multiple sites, campuses or geographic locations, ChurchSuite includes fantastic multi-site functionality that allows you to assign people and other details within in your ChurchSuite database to different sites.
In this article
Setting up your different sites
Assigning user site permissions
Assigning details to sites
Importing data into a multi-site account
Multi-site location reports
Multi-site and My ChurchSuite
Setting up your different sites
The process of setting up your various sites is really simple - it begins with adding each additional site and then assigning the user permissions for each site - without site permissions your users will be unable to access a newly-added site and the data therein! Each ChurchSuite account begins with a single site. This article explains how to add additional sites and how multi-site works across the different parts of the ChurchSuite ecosystem - in ChurchSuite, My ChurchSuite, My Consent, Connect, Embed and Donate. Let's get started...
To add a new site, head into the Administrator area and select the Profile section.
Scroll down the Profile page to the Sites section and click Add site.
On the Add site pop up, enter the Name of the site, optional site Initials (a short abbreviation), the Address and Postcode, and select a site Colour to distinguish your sites on location maps. Click Save before navigating away from the page.
Note how the list of sites can be re-ordered if you wish - perhaps alphabetically or to place a primary site first in the list - either drag the Order number within the list or click on any of the order numbers in the list to open a Reorder pop up.
You can return to the list of Sites at any time in the future to make changes to a site - select Edit from the Action menu on the right-hand side of a site in the list. Notice also the option to Edit location, which can be used to precisely set the map pin location for the site - the site location is used for ChurchSuite's Location reports.
Assigning user site permissions
Still within the Administrator area, switch to the Users section. For each User in turn select Edit from the Action menu.
In the Edit User pop up, locate the Sites section. Select the user's permitted sites (permitted sites change from grey to blue when selected). Note the option to permit just a single site, any combination of multiple sites or All sites. Selecting "All sites" will give site permissions for all current sites and any future sites you may add to your account in the future, without the need to make future changes to the user's site permissions. Save your changes and repeat for each user in turn.
Important - working within permitted sites
When working with people in your ChurchSuite modules, a User can only assign people to one of their "permitted sites", meaning that only a user with "All sites" permissions could assign an Address Book contact to "All sites"; while a user with 'Site A only' permissions could only assign contacts to Site A. In this regard, the User's "permitted sites" determines what they can do. However, when editing a person whose sites include non-permitted sites, those non-permitted site assignments will persist when the record is saved.
Example 1: A user has Site A permissions only. Working in the Address Book, they can edit a Site A contact who also belongs to Site B and C. When they save the changes, the contact will still belong to Site B and C, even though the user doesn't have those site permissions.
Example 2: If that same user edits the contact and selects to un-assign the contact from Site B and C, they will not be able to re-assign them later as only their permitted site will now be listed. Only a Site B and C user can assign Site B & C back to that contact's profile.
Example 3: If that same user edits the contact and selects to un-assign the contact from Site A (user's only permitted site) but leaves Sites B & C assigned, the contact's details will be saved, but the user will no longer be able to access the contact's profile - the contact now belongs to non-permitted sites for that user.
Now, having assigned site permissions, a user with access to multiple or all sites will be able to switch between viewing their permitted sites using the Sites selector in the top-right corner of ChurchSuite; choosing between a specific sites or viewing as All Sites (if they have permissions for all of your sites) or My Sites (if they have permissions for more than one of your sites, but not all of your sites).
For example, this User has permissions for all three sites, so they have an 'All sites' option...
...however, this User only has permission for two of the three sites - they can view specific sites or 'My Sites' (which is all their permitted sites). In this context, the User is unaware of how many sites there are in total - they only know that there are other sites as they don't have an 'All sites' option.
It's helpful to remember that in a multi-site context, a user's experience throughout ChurchSuite is determined by two factors:
- their permitted sites
- the site/s currently being viewed
This is explored further later in this article but, for now, this principle is best illustrated when viewing a Tag, perhaps in your Address Book. For example, some of your Address Book contacts may be assigned to a 'Members' tag. When a user is viewing the tag as "All sites" they'll see all tagged members listed. When viewing as "My sites", the user will only see tagged members for all their permitted sites and when viewing as a single site they'll only see tagged members relating to the specific site being viewed. The user is unable to see tagged members for non-permitted sites.
Here's another example - a Ministry in the Rotas module. A ministry is always site-specific but the ministry may (and can) contain members from different sites to the ministry. If a User's module and site permissions allow them to view the ministry (because the ministry belongs to one of their permitted sites), then that user will always see the full ministry member list, including members belonging to non-permitted sites. In the context of ministries, rotas, gatherings and groups, we never show a user a partial or incomplete list. However, where a user has Address Book permissions, the user is prevented from clicking through to the Address Book profile page of a person belonging to a non-permitted site - an error page is displayed explaining why they can't access the person's profile. This means your users are able to fully manage their ministries, rotas, gatherings and groups without constraint; but they only have access to the underlying people profiles in the Address Book or Children module for those in their permitted sites.
Assigning details to sites
In this section we'll explore in detail where multi-site functionality is surfaced within ChurchSuite and how multi-site data is shown to a user in each context depending on their site permissions and/or the site/s being viewed.
Address Book & Children module - contact details
In the Address Book and Children modules, Sites is a required field for all contacts, children and visitors. When adding a new person you'll select their appropriate Sites. In the following example, the User adding the new contact is an All Sites user, so they have the option to assign the new contact to one, multiple or All sites. However, a Nottingham-only user would only have the option assign the new contacts to Nottingham site.
When editing an existing person, perhaps to make changes to some of their details, a User can un-assign any of the existing Sites but they can only assign new sites based on the user's permitted Sites. A user with restricted site access can always save changes without the person being edited losing previously-assigned sites; so, a user with Nottingham-only permissions can save changes made to a Nottingham and Derby site contact without that contact losing their pre-existing Derby site assignment.
Features, such as Flows, Tags and Key Dates, are not site-specific; they exist across all of your sites. However, the people a User sees listed in a Flow, Tag or Key Date will depend on the site they are viewing as. For example, when viewing a Leaders Tag as "All Sites" the User will see all leaders across all of your sites, but viewing the same Tag as "Site A" only, they will only see Site A leaders listed. This is the same with Flows and Key Dates.
Smart Tags that include a Sites condition can only be viewed as "All Sites" or "My Sites"; the matching contacts or children for the Tag will only show in this context. For example, this tag matches Address Book contacts that are 'South Site parents' - the Tag is only listed in the Tags section and matching results can only be viewed when viewing as "All sites" or "My sites".
Finally, in the Address Book or Children module, you can create and manage multi-site Forms. A Form is either site-specific or All sites. A User viewing a Form's responses will always see a full list of responses, regardless of the site being viewed; however, they will only be able to click through to view a respondent's Address Book or Children module profile for their permitted sites.
In the Giving module, giver profiles have a giver Site. For givers linked to their underlying Address Book profile, the giver's site will typically be the same as the linked contact's site; although this can be optionally overridden in the giver's profile. A giver can only be assigned to a single site - this is to enable site-specific Gift Aid Claims to be produced (UK customers only). While a giver's linked contact may belong to multiple sites you'll need to select just one site for their linked giver profile.
When a new giver makes a donation online through ChurchSuite Donate, the new giver profile is always first added to the default (first) site as listed in the Sites list found in Administrator > Profile; however, you can edit a new giver's profile to assign them to a different permitted site.
When adding a Ministry, or editing an existing one, you must select the Site to which the ministry belongs. Ministries are always site-specific, but you can create a separate ministry for each of your sites. Rotas derive their site from the site of the underlying ministry. A User with permitted site access to view a ministry, role, rota or service will always see the full member list for that ministry/role/rota/service, even if the list includes people belonging to non-permitted sites. In this situation, the User will only be able to click through to a person's underlying profile in the Address Book or Children module for those assigned to permitted sites.
While a User working within the Rotas module can add new ministry and rota members from any permitted site, designated ministry overseers creating and managing rotas within My ChurchSuite can only add new ministry and rota members from the ministry's site (regardless of the sites that the overseer may belong to). However, a Rotas module option is available to determine whether ministry overseers can add member's from Just the ministry's site (the default) or All sites.
Small Groups module
When adding a small group, or editing an existing one, you must select the Site to which the group belongs. Groups can be either site-specific or All sites. A User with permitted site access to view a small group will always see the full member list and attendance for that group, even if the list includes people belonging to non-permitted sites. In this situation, the User will only be able to click through to a person's underlying profile in the Address Book or Children module for those assigned to permitted sites.
While a User working within the Small groups module can add new group members from any permitted site, group members with the appropriate role permissions (typically leaders) can add new group members from the group's site (regardless of the site/s that the overseer may belong to). However, a Small Groups module option is available to determine whether group leaders can add member's from Just the group's site (the default) or All sites.
Finally, designated cluster overseers can always see the group, member list and attendance for all groups within their cluster (regardless of the site/s the overseer may belong to, and regardless of the site/s the cluster's groups belong to)
Within the Children module, children and youth Gathering are site-specific. You create separate Gatherings for each of your sites where your children or youth ministry operates. The Groups for each Gathering derive their site from the Gathering. When viewing a group, a User is able to see the full group member list and group attendance data, even if some of the children, visitors or team belong to different sites to the Gathering. However, the user is only able to click through to view the full child, visitor or team member profile for those who belong to permitted sites. When viewing a child's profile, a User will see the child's full attendance for all Gatherings, including Gatherings for non-permitted sites. A User can only add children to groups from the user's permitted sites.
In the Calendar module, events are either site-specific or All sites; it's not currently possible to create events that exist in multiple sites i.e. some sites but not all sites.
The categories you create in the Attendance module are always site-specific, so you'll create a separate list of categories for each of your sites.
When entering each week's attendance data, you will select the Site and specify the Date for the data being added, adding a separate set of data for each site per date and for just the categories of that site.
Within the Bookings module, a Site is specified for Resources. Resources are either site-specific (e.g. rooms) or shared across All Sites. For example, a clergy member responsible for funerals could be created as an all sites resource so that they can be assigned to funeral bookings for any site.
When adding a booking, you will specify the booking's Site. The booking's site will also determine the resources that can be assigned to the booking. Only 'All sites" resources and resource of the same site as the booking can be assigned to the booking.
Within the Planning module you can specify a Plan's site - Plans can be either site-specific or accessible across All sites.
If a Plan is linked to a Service, Event or Booking, the Plan follows the same site setting of the linked item, as follows:
- When linking a Plan to a Service, the Plan site will be set to "All sites". While rotas and their underlying ministries are site-specific, Services do not themselves have a site. Typically a service will likely be a grouping of rotas from the same site, however, it's entirely possible and sometimes desirable to group rotas from multiple sites into a Service. With this in mind, and to ensure the Plan's "people criteria linking" is able to detect the members of all the rotas related to a service (regardless of those rota's sites), Plans linked to a Service are added as "All sites". You can optionally edit a Plan's site and set it site-specific if you wish, but be aware that the Plan's "people criteria linking" will only detect people from rotas of the same site as the Plan.
- When linking a Plan to an Event, the Plan site will be set to the same site/s as the event - either site-specific or All sites.
- When linking a Plan to a Booking, the Plan site will be set to the same site as the booking - bookings are always site specific.
- When adding a Plan that is not linked to a service, event or booking, you can set the Plan's site to be either site-specific or All sites.
Importing data into a multi-site account
We've produced comprehensive support articles that explain how to prepare and present your existing data for import into ChurchSuite - see the related support article links at the end of this article.
Briefly though, to ensure imported people are assigned to the correct sites, Sites should be specified as a column within your import CSV. The import value specified for each person's Sites will be either a single specified site, multiple sites that are specified semi-colon separated, or left blank for 'All sites'. The site-naming convention in your CSV file must precisely match the site-naming convention in ChurchSuite.
Since a user can only import data to their permitted sites, the import process is best completed by an "All sites" User viewing the module as "All sites". You can use the Sites selector to change between different sites before you import data for each site.
A visual site avatar indicates the site currently being viewed.
Multi-site location reports
When viewing any of ChurchSuite's location reports as All Sites and My Sites (E.g. "Address Book" > "Reports" > "Locations") each site and its respective contacts are shown in a different colour on the map view. Up to five different colours (red, blue, green, orange, yellow) can be shown, so each site will show in its own colour.
For multi-site locations to work correctly, you must specify the correct postcode/zip code for each Site in the Profile section of the Administrator area. You can set each site's location more accurately using the Edit location option...
...to zoom in and drag the map pin marker to the correct position. Click OK to save the updated map pin location for the site.
Multi-site and My ChurchSuite
ChurchSuite's member-facing My ChurchSuite platform also supports multi-site functionality.
My ChurchSuite includes a great optional "Search for Others" contact directory, making it easy for your members to stay in touch with one another, while always respecting privacy settings in the search results. When enabled, and by default, the search functions across the contact's own site/s. For example, a Nottingham site contact will be able to search across Nottingham contacts only. Where you wish to enable a broader search, an Address Book module My ChurchSuite Option is provided to Allow contact to search across All sites.
When searching for members across "All sites", the member's site is surfaced in their contact details pop-up. The personal data surfaced in the pop-up is determined by the member's privacy settings.
Please read this section carefully BEFORE deleting a site. Deleting a site is irreversible!
Sites are managed in the Profile section of the Administrator area - select Delete from the Action menu for the site to be deleted.
When deleting a site, it's helpful to understand what happens to the existing module data related to the site being deleted. Since site deletion has irreversible consequences, the User is required to select and confirm the New Site the existing site data is to be re-assigned to, followed by an "I CONFIRM". If there is only one site remaining, that alternative site will be pre-selected and all site-specific data will be re-assigned to that one remaining site.
If you do not want site data to be re-assigned - perhaps because you no longer wish to retain some or all of the data for that site - it should first be deleted within each module before deleting the site, as it may be more difficult to identify the deleted site's original data once it has been re-assigned and merged into another site's data.
Note that your original/first site is always assigned a site ID of "1". Sites subsequently added will be assigned the next consecutive site ID number. Even if you re-order your sites in the list (perhaps so that site ID_1 is no longer the first site listed), the Site with ID_1 cannot be deleted.
What happens to the data in each module when a site is deleted?
Address Book - Contacts (active, archived and pending) are re-assigned to the New Site. No contacts or their associated data are deleted. Contacts continue to be linked to the spouse/partner and children.
Children - Children (active, archived and pending) and Visitors are re-assigned to the New Site. No children or visitors or their associated data are deleted. Gatherings, and their associated groups and historic session attendance are re-assigned to the New Site. Children continue to be linked to their linked parent(s).
Attendance - all site-specific attendance categories, and the associated historic attendance data in those categories, will be re-assigned to the New Site.
Calendar - all site-specific events (past and future) will be re-assigned to the New Site. User Leave setups and requests are unaffected by a site deletion. Bookings and Plans remain linked to the events.
Small Groups - all site-specific groups (past, active and future) will be re-assigned to the New Site. All historic group attendance is retained.
Rotas - all ministries (active and archived) and their related rotas will be re-assigned to the New Site.
Giving - givers - whether linked to contacts or unlinked (active and archived), along with all their associated donation data, pledges and Gift Aid declarations, will be re-assigned to the New Site, and linked givers will remain linked.
Giving (UK only) - the integrity of previously-submitted Gift Aid claims are preserved unaffected by a site deletion. Each claim's list of givers and donations remain in tact and the claim remains accessible to view.
Each site has its own Small Donations Scheme (SDS) giver profile, a "system" giver profile that gets added when a new site is added. When a site is deleted, if there are no historic donations linked to the SDS giver, it is deleted. If, however, there are historic donations, the SDS giver profile is preserved, re-assigned to the New Site and renamed e.g. Small Donations [site name] (Deleted]).
Bookings - bookings (past and future, active, pending and cancelled) are all re-assigned to the New Site. Site-specific resources are also re-assigned to the New Site.
Planning - unlinked plans (past and future, draft and published) are all re-assigned to the New Site. Plans that are linked to events, bookings or services continue to be linked and will inherit the New Site for those events, bookings and rotas as explained above.
Administrator - site permissions for the site being deleted are removed from each user account. A User account with site permissions for only the site being deleted will be preserved, but will be unable to log in. They can be manually assigned site permissions to other sites, or you might archive or delete their user account if no longer required. Be aware that deleting a User will also delete the related leave setup and historic leave requests. Additionally, any tags, notes, key dates or flows that they have set visible to "Just me" will no longer be accessible.
- Smart Tags with a deleted "Site" condition will break and need to be manually updated. Bear in mind that those smart tags may be being used for event and external link visibility restrictions in My ChurchSuite, and tag-syncing may be being used in a MailChimp integration.
- When contacts, children and givers are re-assigned to a New Site, their addition to the New Site will affect future site-specific reporting and Smart Tags in the New Site. One consequence might be that new subscribers are added to your Mailchimp audience via the sync tags that now include re-sited people.
- Synced contacts in your Planning Center integration will continue to be synced.
- Address Book and Children module statistics (seen in the Statistics report in each respective module) are retained for the deleted sites.
- Any embedded ChurchSuite forms or pages on your website with site-specific embed customisation, including the Address Book embed, Small Groups list and map embed, Calendar embed, and Featured Event embed - these will all break and new HTML embed code will need to be generated and re-embedded in your website.
- My ChurchSuite access for re-assigned contacts is unaffected by a site deletion, but the people they can search in "Search for Others" will change to reflect their new site assignment.
- Use of site-specific JSON feeds or API applications may also break and need to be updated.
- You may need to review and update your Data Protection policy and Privacy Notice to reflect any change of use of people's personal information resulting from their information being re-assigned to a New Site. Remember, their personal data will be merged into a New Site, with the potential for their personal information to now be accessed by different users in ChurchSuite or visible to different members in My ChurchSuite. In most regions, this change of processing will likely require the data subject's prior consent. You should seek professional legal guidance to see how a site deletion and re-assignment of "people data" to a New Site affects your organisation.