To comply with PowerSchool’s partner integration standards, OpenApply now requires schools to install a dedicated server-side plugin—"OpenApply PowerSchool Sync"—on their PowerSchool SIS. This upgrade affects only the configuration and credentialing process, not the core sync logic itself. Schools that previously relied on PowerSchool’s platform plugin must transition to the new dedicated plugin to ensure uninterrupted sync and future compatibility.

By updating to this new plugin, school IT teams gain more control over data permissions, enhanced compliance, and clear credential management. The change is essential for maintaining a secure, reliable link between OpenApply and PowerSchool.

Overview

The dedicated OpenApply PowerSchool Sync plugin enables secure, standards-compliant integration between OpenApply and PowerSchool. Schools must install this plugin on their PowerSchool servers to generate OAuth credentials that authorize the sync. The update affects only the configuration process: there are no changes to what is synced or how.

• Target Audience: IT administrators responsible for managing PowerSchool and OpenApply integration.
• Headline Value: Enhanced security, compliance, and ongoing compatibility through a provider-maintained plugin.

What's New

• A dedicated "OpenApply PowerSchool Sync" plugin (v1.3.3)—available for download and installation on your PowerSchool server.
• The plugin grants OpenApply its own OAuth credentials, ensuring access is authorized and limited to necessary fields.
• Configuration is now fully compliant with PowerSchool’s partner requirements.
• The plugin is required for all future releases and ongoing technical support.
• No changes to OpenApply’s sync interface or mapping logic—shift is solely to secure plugin management.
• Download the plugin archive (.zip) here

Step-by-Step Navigation

If the plugin is not yet installed on your PowerSchool Server

PowerSchool Admin > System Management > Server > Plugin Configuration

1. Download the OpenApply PowerSchool Sync plugin archive (openapply-powerschool-1.3.3.zip).
2. Log in to your PowerSchool Admin interface.
3. Navigate to System Management > Server > Plugin Configuration.
4. Click Install and upload the unzipped plugin file (not the .zip itself).
5. Enable the plugin after installation.
6. Open the plugin’s Data Provider Configuration page.
7. Copy the Client ID and Client Secret provided.
8. In OpenApply, go to Settings > PowerSchool.
9. Paste the Client ID and Client Secret into the matching fields.
10. Set the plugin selector to OpenApply PowerSchool Sync (not "PowerSchool Platform").
11. Save and test your connection.

If the plugin is already installed on your PowerSchool Server

PowerSchool Admin > System Management > Server > Plugin Configuration

1. Log in to PowerSchool Admin.
2. Navigate to System Management > Server > Plugin Configuration.
3. Locate OpenApply PowerSchool Sync in the plugins list.
4. Enable it if it isn’t already enabled.
5. Go to Data Provider Configuration for the plugin.
6. Copy the Client ID and Client Secret from this screen.
7. Open OpenApply and navigate to Settings > PowerSchool.
8. Paste the new credentials in the Client ID and Client Secret fields.
9. Ensure the selector is set to OpenApply PowerSchool Sync, not "PowerSchool Platform".
10. Save your changes and test the connection.

Tips & Best Practices

• Always check if the plugin is already installed before uploading a new copy — some schools may find it pre-installed by Faria.
• Save your OAuth credentials in a secure location. Each school's PowerSchool generates unique credentials, which cannot be reused across schools.
• Use the OpenApply configuration guide for a detailed explanation of settings and field mappings.
• Test the connection after saving new credentials to confirm sync is working before closing settings.
• Document your plugin version and credential update date for internal auditing.

Warnings & Important Notes

• No update to OpenApply software is required; all changes occur on the PowerSchool server and in credential settings.
• Faria Support cannot confirm plugin installation status on your server. Only local PowerSchool Admins have this access.
• Be aware that credentials are unique to each school’s PowerSchool setup—never share or cross-use these codes between environments.
• The "PowerSchool Platform" plugin will be deprecated and unsupported for OpenApply; transition immediately to avoid disruption.

Frequently Asked Questions

Does this change affect the student/contact sync logic in OpenApply?

No—the sync behavior, including field mapping and update logic, remains exactly the same. Only the authentication and plugin management process changes.

What should I do if I see both "PowerSchool Platform" and "OpenApply PowerSchool Sync" plugins in my selection?

Select OpenApply PowerSchool Sync in both PowerSchool and OpenApply. Do not use or select the legacy "PowerSchool Platform" plugin for OpenApply sync moving forward.

Do I need to contact Faria if the plugin isn't listed in my PowerSchool?

First, check thoroughly in System Management > Server > Plugin Configuration. If the plugin is missing, use the provided download link and install it. Reach out to Faria Support only if you have issues with the plugin archive or installation process.

Can I use OAuth credentials from another school?

No, each school’s PowerSchool instance generates unique credentials. They are not transferable and must not be shared across schools.

Is any change required to OpenApply's user interface configuration?

No, the only updates are to plugin selection and credential fields in OpenApply Settings under Settings > PowerSchool.

In Summary

• Install and enable the "OpenApply PowerSchool Sync" plugin for secure, supported integration.
• Update credentials and plugin selection in OpenApply to avoid sync disruption.
• The sync logic remains unchanged—this is a standards and compliance update for your PowerSchool server.

For a seamless experience and ongoing support, always use the required plugin and follow the steps above in OpenApply.