Changing your ChurchSuite or CharitySuite subdomain

The subdomain is your church or organisation account name and forms the first part of the URL used to access ChurchSuite or CharitySuite in a browser e.g. subdomain.churchsuite.com or subdomain.charitysuite.com. Your subdomain can be changed on request, perhaps if your organisation changes its name or you wish to use a more memorable or abbreviated subdomain. You can also request to switch your account domain to churchsuite.com or charitysuite.com.

The ChurchSuite support team can check subdomain availability on request (or offer alternative or similar subdomain suggestions). Changing a subdomain name only takes a few minutes to process once actioned, preferably at a time when users are logged out and will be least affected. If they are logged in, they may lose the changes they are making, or lose access to the data they are viewing and will be required to reauthenticate with the new subdomain URL.

Before changing a subdomain, you should consider the following consequences, which will need to be communicated to your users beforehand and may also need to be communicated to your members.

What happens when the subdomain name is changed?

1. Usernames and passwords are unaffected by a subdomain change; however, users will need to update any saved shortcuts or browser bookmarks for the old subdomain login page and browser users may need to reselect their church/organisation name when logging in for the first time after the subdomain change.
2. All iCal feed subscriptions for calendars, bookings and rotas will break and will need to be resubscribed.
3. Any web-embedded ChurchSuite/CharitySuite content will break, including My Details, small group embed, calendar embed, featured events feed, network embed, embedded event pages and embedded Donate links.
4. All previously shared public-facing page and form links will cease to work and will need to be reissued or shared. This applies to events pages, fund pages, group pages, booking pages, My Consent pages, communication pages, rota pages, plan pages and form pages.
5. App users running v4.0.20 or newer (Android and iOS) will remain logged in the app and their ChurchSuite/CharitySuite and My ChurchSuite/My CharitySuite accounts will persist in the app "Accounts" drawer. Immediately after a subdomain change, eager app users will need to re-select each account from the "Accounts" drawer to force the 'web view' account cache to update; otherwise, users will experience page errors or unexpected redirects when trying to navigate their app Menu. After 24 hours, the app's 'web view' account cache will expire and automatically refresh, so most app users will experience no noticeable impact 24 hours after a subdomain change. Importantly, app users running v4.0.20 or newer will not be logged out.
6. App users running v4.0.19 or older will be logged out of their apps and will be required to re-authenticate. In some circumstances, the app may become unresponsive, which will unavoidably require the app user to delete and reinstall the app to re-authenticate.
7. Desktop and smart device shortcuts will break and will need to be re-made under the new subdomain.
8. Child check-in kiosk mode in Chrome under Windows will need to be re-created with the new kiosk mode URL for your new subdomain.
9. Any API applications and JSON feed code will need updating to contain the new subdomain URL for "calls".

How to request a subdomain name change

Your organisation's designated account contact will need to request the change in writing by email.