This article is about Scopes.
Which integrations are involved?
Breeze: Breeze grants access to all API services via the API KEY. So, Scopes is not required.
Pushpay/Church Community Builder (CCB), Google Calendar (GCal), and Planning Center (PCO) all use Scopes.
How did it start?
As you know, part of the integration process is making sure Display.Church has the required permissions from your ChMS or external app. The permissions needed depend on your integration and what kind of calendar/groups views you are using.
However, the situation is not a ‘one and done’. You or your staff can change connected account permissions at any time whether accidentally or on purpose. These changes can cause your Display.Church views to have display issues.
What are we doing now?
Before each sync, we will recheck the permissions situation. If all is well, we do the sync. If something is off, we will stop all automatic syncing, add a notice in your Display.Church account, and send you an email.
For some of you, especially CCB users, you may get this error as we are making more services mandatory for easier coding. They will be grouped by feature (Events or Groups).
We feel that this improvement will reduce the number of display issues overall.
For those of you who are more 'tech' oriented, here is a diagram of our logic:
Scopes when you set up your Integration
 | You will find it on the Integrations page when you set up your integrations.
To get to the Integrations page, look at the main menu in the left-hand most column of your screen. Choose Integrations.
|
CHURCH COMMUNITY BUILDER (CCB)
You will see Scopes after you click on Start integration.
Mandatory: This first item is a must. It is automatically turned on by Display.Church.
Calendar: Allow Display.Church to pull all your events from your public, groups, and individual calendars.
Groups: Allow Display.Church to pull basic information about your groups.
RSVP: This scope is used when a person RSVPs to an event.
Check the items you wish to use. The box will turn blue.
Uncheck the items you do not wish to use. The box will be white.
GOOGLE CALENDAR
You will see Scopes after you click on Start integration.
Public profile: This first item is a must. It is automatically turned on by Display.Church.
Calendar API: This allows Display.Church to see and pull in your Google calendar event details. If you do not give this permission, your Display.Church calendar will display without events.
Events Attachments (optional) : We ask for this permission so we can display your event images. Display.Church is set up to pull in the first image which is attached to each Google Calendar event. This makes your Display.Church calendar view even more eye-catching and attention-grabbing. And as we know, images are powerful helpers–boosting the messages in our words. So, we strongly suggest giving us access.
Places (optional) : We ask for this permission so we can pull in location information attached to your events.
Check the items you wish to use. The box will turn blue.
Uncheck the items you do not wish to use. The box will be greyed out.
*** A NOTE ABOUT GIVING GOOGLE DRIVE ACCESS ***
Display.Church is an approved-by-Google 3rd party app. In other words, we were authorized (after extensive review) to access the Google API services. In addition, we are governed by our own strict privacy and terms. We take your privacy seriously. When you enable the Drive API, we will only pull in the image attached to the event.
Having said that, should you still feel unsure, you do not have to give access. The only limitation is that Display.Church will not be able to pull in your event images.
PLANNING CENTER (PCO)
Find Planning Center (PCO). Click on the Start integration button.
NOTE: The button will turn blue as you hover over it.
You will see Scopes after you click on Start integration.
People: This first item is a must. It is automatically turned on by Display.Church.
This scope is necessary in order to retrieve the authentication and refresh tokens for the PCO API. There are no alternatives. https://developer.planning.center/docs/#/overview/authentication
In the future, we hope that PCO enhances this by relocating the authorization requirements to a distinct end-point. Rest assured, we do not access any of your people information outside of the mentioned tokens and the name of your account.
Calendar: Permission to pull your events from the PCO Calendar service.
Groups: Permission to pull your groups so you can filter events by groups.
Registrations: Permission to pull your publish registration/signups from your Church center so you can link directly to them in your calendar views.
To find your churchcenter name, log in to PCO and click on registrations.
Click on the Church Center downward arrow. Choose Visit on Church Center.
The name you need is the text BFORE the '.churchcenter' (see blue box in image below for position of the text you need).
Check the items you wish to use. The box will turn blue.
Uncheck the items you do not wish to use. The box will be greyed out.
SCOPES ON A DAY-TO-DAY BASIS
First, let's look at what emails/notifications you will see.
Then, we will talk about what you need to do. [Skip the examples and jump to this section.]
Examples of what you will see
Please keep in mind that the actual email/notification will depend on your integration and the scope(s) in question.
Email for CCB
Email for GCal
Email for PCO
CCB Integrations page
GCal Integrations page
PCO Integrations page
--------------------------------------------------------------------------------------------------
WHAT YOU NEED TO DO
 | In general, you need to log in to Display.Church and go to your Integrations page.
Once there, you should see a notification which will explain what you need to do. Click on the Read more. Using the CCB integration?Before you follow the steps in the Display.Church notification, make sure all the necessary API services are enabled.
Using the PCO Integration?Before you follow the steps in the Display.Church notification, make sure that the user logged in to D.C has access to the PCO permissions you are enabling. Read more.
A little vague?True, but there are so many combinations of what could need fixing that we cannot give steps for each one. Scroll down for some examples.
Need more support?No problem - our online chat awaits. Yes, the first step is automated but you know you can always talk to a human. |
FOR EXAMPLE
(1) You see this message on your Integrations page (image below):
(2) You click on the Read more (image below):
This message means that you are trying to sync using Groups but you are not authorized to do so.
(3) Here is what your Integration page looks like for this integration (image below):
As you can see in the image above, Groups is indeed checked.
In this case, you would need to uncheck Groups and then click on the blue Re-authenticate button.