What would you like to know more about?

Show Page Sections

Church Online Platform

Church Online Platform (ChOP) is a free tool for churches to launch an online ministry. With ChOP, you can broadcast church services, provide live chat, offer live prayer, and more to help create community. This integration supports a single sign-on (SSO) experience for your church body using their MinistryPlatform accounts.

Data in MinistryPlatform

If you create a User record through this integration, that information displays on the Users page.

Cost

There is no charge from ACS Technologies for configuring the integration.

Support

Contact MinistryPlatform Support for assistance.

Resources

Single Sign-On Setup Overview

  • You must have an account with ChOP before you configure the integration with MinistryPlatform.
Warning: Plan Ahead. This change may be disruptive. After you enable single sign-on, some users may need to reset some of their settings.

Admin Accounts: Double check your admin accounts, or you may lose access to your ChOP admin screens.

Pick the Right Day: We highly recommend you set up this integration with a few days' buffer before your next online service.

One-way Street: If you make a mistake initiating this integration, you must contact ChOP Support to reverse the changes.

  1. Create a new Church Online Platform API Client.
  2. Create a new complex secret.
    Tip: We recommend using the Password Generator to generate a secure value. Click the magic wand icon wand with surrounding stars beside the field to open the Password Generator and select the options you want.
  3. Set up the proper redirect URI (copied from ChOP Admin screen).
  4. Ensure that the Admin Account exists in the Platform with the same email address as the current Admin.
  5. Make configuration changes to ChOP.
    Note: When you test the configuration in ChOP, you will see an error message about an "invalid scope". Don't worry, this is expected. As long as the error only refers to an invalid scope (and not an issue with your connection, client, or secret), you can continue with the integration.
  6. Test the login.
Want to watch someone walk through all the steps to integrate MinistryPlatform authentication with ChOP? This video shows an older Platform interface, but the information is still relevant. Check it out if you need a little extra help!

ChOP Integration FAQ

Q1: Can I link multiple instances of ChOP to a single Platform instance?

Yes, you can link multiple instances of ChOP to a single Platform instance. We set up two instances and map them back using separate API calls so we can identify which ChOP instance is used to log in.

Q2: What do people's display names and avatars look like in ChOP after the integration is turned on?

At this time, "current" users are bypassed. ChOP creates a "new" user record tied to the Platform user. You can then customize that user with a proper display name and image.

Q3: Since ChOP user profiles are bypassed, how do we create and manage ChOP admins and volunteers to assign host roles and titles? Can we do that in ChOP after the integration is in place and as long as their emails match in MinistryPlatform it correctly gives them the proper permissions?

You can still assign new host roles. You can't assign older (pre-OIDC) hosts and roles, but you can update the MinistryPlatform user account (in ChOP) with new roles.

Q4: How can we avoid confusion for users switching from using an email address to log in to ChOP to their Platform username (which may not be an email address)?

Consider turning on Simple Sign-On so your users can use email OR username OR mobile phone number.

Q5: Will I lose admin access if my Platform username is not my email? Does my Platform username need to match the email address of the existing ChOP admin? Or does the OAuth or OIDC process match my contact record email?

We recommend you test everything first. Don't be afraid to spin up a new ChOP and test it all yourself before you switch over.

Q6: When I test the configuration in ChOP, I see an error message about an "invalid scope". What do I do?

Don't worry! This is an expected error due to the way ChOP tests whether our systems are good to go. As long as the error only mentions an invalid scope, you can continue with the integration. If there's an additional error, such as an issue with your connection, client, or secret, you'll want to walk through the setup steps again to be sure everything is correct with the integration.

thumb_upYes thumb_downNo