• Overview
  • Configuration

PowerSchool

Automate staff and student account creation by connecting PowerSchool with ADManager Plus.

Identity provisioningHCM

PowerSchool is a widely used student information system (SIS) for K–12 institutions. Integrating PowerSchool with ADManager Plus allows schools and districts to synchronize user life cycle events between PowerSchool and Active Directory (AD). When a student, teacher, or staff account is created, modified, or deactivated in PowerSchool, ADManager Plus can automatically perform the corresponding action in AD. This ensures timely account provisioning, accurate access control, and secure offboarding.

 

Onboarding automation

Automatically create AD user accounts when new students or staff are added in PowerSchool.

 

Account updates

Reflect changes to user attributes such as grade level, department, or role in AD based on updates in PowerSchool.

 

Account deactivation

Disable or delete AD accounts when users are marked as inactive or removed from PowerSchool.

 

How to integrate PowerSchool with ADManager Plus

Pre-requisites

PowerSchool uses OAuth 2.0 to authorize API requests. Please ensure the client_id and client_secret with permissions are provided to retrieve desired information and perform tasks in PowerSchool. Refer to the PowerSchool API references page for more details.

Privileges

  • To import users (inbound action): Ensure the account used for authorization has permission to read all user accounts.
  • To perform any action or query in PowerSchool (outbound action): Ensure the account used for authorization has permission to perform the desired action.
Note: ADManager Plus comes with a preconfigured set of APIs that help perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from the PowerSchool API documentation to configure the inbound or outbound webhooks to perform the required actions.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search for and select PowerSchool.
  • Toggle the Enable PowerSchool Integration button on.
  • In the PowerSchool Configuration page, click Authorization.
  • Perform the steps to generate client_id and client_secret from PowerSchool.
  • Replace {POWERSCHOOL_SERVER} in the Access Token URL with the value of your PowerSchool instance.
  • Select Grant Type as Client Credentials.
  • Click Configure.

Inbound webhook configuration

The inbound webhook enables you to get user data from PowerSchool to ADManager Plus and perform desired actions using the Automation feature. To configure an inbound webhook for PowerSchool:

  • Under Inbound Webhook, click PowerSchool Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, PowerSchool Get All Students Endpoint, comes preconfigured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from PowerSchool. If you would like to use this preconfigured endpoint, replace {POWERSCHOOL_SERVER} with the values of your PowerSchool instance in the Endpoint URL field. However, if you would like to use a new endpoint to import users, you can configure one using the + Add API endpoint button and filling in the required fields per PowerSchool's API references. Click here to learn how. Note:
    • The Authorization Header is preconfigured for authenticating API requests as formatted during Authorization Configuration.
    • You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component.
    • Refer to PowerSchool's API references and configure additional headers and parameters, if required.
  • Once done, click Test & Save. A response window will display all the requested parameters that can be fetched using the API call. Click Proceed. Note:
    • Refer to PowerSchool's API references to learn the Parameters that must be configured to fetch specific parameters.
    • You can configure multiple endpoints for PowerSchool using the + Add API endpoint button. Click here to learn how.
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in PowerSchool.
  • Click + Add New Configuration and perform the following:
    • Enter the Configuration Name and Description and select the Automation Category from the drop-down menu.
    • In the Select Endpoint field, select the desired endpoint and a Primary Key that is unique to a user (e.g., employeeIdentifier). Note: When multiple endpoints are configured, this attribute must hold the same value in all the endpoints.
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective column in PowerSchool.
    • If you would like to create a new custom format for this, click Add New Format.
    • Click Save.
Note: The attribute mapping configured in this section can be selected as the data source during automation configuration to perform the desired action on the list of users received from the API response.

Outbound webhook configuration

An outbound webhook enables you to send changes made in AD using ADManager Plus to PowerSchool and carry out tasks in PowerSchool—all from ADManager Plus. To configure an outbound webhook for PowerSchool:

  • Under Outbound Webhook, click PowerSchool Webhook Configuration.
  • Click + Add Webhook.
  • Enter a name and description for this webhook.
  • Decide on the action that has to be performed and refer to PowerSchool's API references for the API details, such as the URL, headers, parameters, and other requirements.
  • Select the HTTP method that will enable you to perform the desired action on the endpoint from the drop-down menu.
  • Enter the endpoint URL.
  • Configure the Headers, Parameters, and Message Type in the appropriate format based on the API call that you would like to perform.
  • Click Test and Save .
  • A pop-up window will then display a list of AD users and groups on which to test the configured API call. Select the desired user or group on which this API request has to be tested and click OK. This will make a real-time call to the endpoint URL, and the selected objects will be modified according to the configuration.
  • The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.
Note: The webhooks configured in this section can be included in Orchestration Templates, which can be used in event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (under Management > Advanced Management > Orchestration).