What are Personal Access Tokens?
Planning Center has public APIs so churches can connect their data to other tools, apps, and services. For years, this has powered integrations like ProPresenter, Clearstream, Zapier, and custom reporting dashboards your team might already use today! There are two main ways for a tool to use the API: as a connected app (what most third-party integrations use) or through a Personal Access Token (what this update is about).
A Personal Access Token (PAT) lets a user on your team connect their own scripts or integrations to Planning Center, using their own permissions. Common uses include:
Setting up a Zapier automation to sync data between systems
Running a reporting dashboard or custom script
Backing up or exporting data on a schedule
PATs are created by individual users, not administrators. Until now, Organization Admins had no way to see what tokens existed in their church or who owned them.
See every token in your organization
:quality(75))
A new Personal access tokens tab on Account Settings โ Integrations โ Personal access tokens lists every PAT in your org for organization admins to see and take action on:
Owner: Who created the token.
Name: The label the user gave it.
Created: When the token was first made.
Last used: The most recent tracked activity. If empty, reach out to the token owner to confirm.
Status: Active or Revoked (with reason).
Revoke: One click to retire the token.
Revoked tokens are hidden by default. Toggle Show revoked to see them along with the reason they were revoked.
Revoke a token in one click
As an organization admin, if you see a token belonging to a former staff member or an unfamiliar integration, click Revoke to remove access. The token is immediately deactivated, any scripts using it will stop working, and the owner receives an email letting them know.
Automatic cleanup when a user is set to inactive
When you set a user to inactive, any Personal Access Tokens they own are now automatically revoked. The Set inactive dialog shows a heads-up when the user owns PATs so you know what will happen before you confirm.
Why we made this change
Personal Access Tokens have grown significantly in 2025 and continue to accelerate in 2026, driven largely by automation platforms and AI tools. Until now, Organization Admins had no visibility into what tokens existed in their organization or who created them. These changes ensure admins can see and manage all API access in one place.
๐ The API Team
