This article gives our best advice about setting up your Planning Center (PCO) API User.
OUR RECOMMENDATION
We strongly recommend creating a unique PCO profile just for the Display.Church--PCO integration. In this way, this user will always be with your organization regardless of staff changes within your church. We don't recommend using your own or an existing staff member or volunteer PCO profile for this integration.
MORE ABOUT WHY WE RECOMMEND THIS
Things change. People come and go.
The person who was your PCO admin when you joined Display.Church (D.C) might have left the church, been made inactive, or their admin privileges were revoked for whatever reason.
If the log in details that were used to set up the D.C -- PCO integration were their personal log in details, you will most likely have access issues.
HOW TO FIX ACCESS ISSUES
OPTION 1
Go back to the person who set up the integration and ask for the login they used. This is more than likely going to require some investigation on your side to find out the exact issue. You will need to restore the user back in PCO if they were made inactive or their privileges were revoked, update the password if it changed, or create a new one for the integration.
OPTION 2
(1) Create a new, dedicated PCO profile, with admin privileges, just for the Display.Church--PCO integration.
According to Planning Center as of 2024.01.10, you can update a person's permissions from the Actions menu in that person's profile.
Here is the Planning Center helpdesk article for more information: https://pcopeople.zendesk.com/hc/en-us/articles/204462570#GiveAccess
(2) Re-authenticate your D.C -- PCO integration. Everything will remain (filtering options, etc.) as we use your integration's internal keys/ids. However, you will have to re-connect every widget to that new integration.